durin
Sign up
Connections & MCP

How to add Atlassian (Jira) MCP

Prepare an Atlassian (Jira) connection and understand the setup requirements before adding its Durin URL to an agent.

Check the supported setup path

The Atlassian (Jira) library profile uses https://mcp.atlassian.com/v2/mcp?tools=all for the flat tool catalog. The current Custom MCP form rejects query strings, while the named provider card does not supply this endpoint. This profile needs deployment work before self-service setup can finish.

Save or request the installation

Name the connection for the intended provider workspace so it can be distinguished from other installations.

  1. As an administrator, open Connections → All providers and choose Atlassian (Jira).
  2. Choose User signs in and OAuth, enter registered client details if your deployment owner supplies them, then save the draft.
  3. As a member, request the provider from Available connections instead. An approved request still requires setup.

Continue after runtime support is available

Follow Add a provider connection: complete provider consent, discover tools, save permission review, obtain its validator release, run a reviewed read test and accept the activation preview. Keep the connection disabled until every checkpoint passes.

After activation, complete personal provider access and copy the connection URL. Follow MCP client setup to authenticate your agent and verify the reviewed read.

Troubleshooting

Can I remove the endpoint query parameters?

No. tools=all selects the flat catalog needed for individual review. Ask the deployment owner for reviewed support for that exact endpoint.

Frequently asked questions

Does the provider adapter activate this connection?

No. Library fixtures do not establish live provider acceptance or implement the missing setup path.

Try Durin with your MCP workflow.

Create an account to connect a client, route governed MCP requests, and review decisions with your admins.

Create an account