Atlassian MCP server
Jira and Confluence, without leaving the record you work on. Standards ships an MCP client. Atlassian connects from your workspace settings, with no code, and its tools become usable by your agents under your roles and permissions.
Atlassian requires OAuth, which Standards does not yet open to MCP servers. The OAuth engine already runs for mailboxes and calendars: this integration follows in the next release.
How to connect it
- 01Open the workspace settings, Integrations section.
- 02Add a custom server and paste the address below.
- 03Enter the key if the server asks for one, then confirm.
- Authentication
- OAuth soon
What the server exposes
The server requires a key, so its tool list is only readable once connected. It shows up in your settings on first connection.
Once connected
The Atlassian tools join the ones in your workspace. An agent can call them mid-conversation, attach what it gets to the right record, and every call goes through the audit log. Sensitive actions still require human approval.