How to connect Atlassian Jira/Confluence in Fleet

Last updated: June 10, 2026

To connect Atlassian Jira/Confluence to Fleet, you have two options depending on how you want to handle auth:

Option 1: OAuth 2.1 (per-user, recommended)

  1. In Atlassian admin (admin.atlassian.com) > Rovo > Rovo MCP server, add your LangSmith domain to the allowed domains list (e.g. https://<your-subdomain>.<your-company>.com/**)

  2. In LangSmith: Org Settings > MCP servers > Add server

    • URL: https://mcp.atlassian.com/v1/mcp

    • Auth: OAuth 2.1 (Auto)

  3. Click Connect and approve Jira/Confluence/Compass access

  4. Each end user will need to complete the OAuth flow once in their Fleet session

Option 2: API token with shared service account

  1. In Atlassian admin > Rovo > Rovo MCP server > Authentication, enable "Allow API token authentication"

  2. Create a service account user with access to the relevant Jira projects and Confluence spaces

  3. Sign in as that service account, go to https://id.atlassian.com/manage-profile/security/api-tokens, create a token with "Create API token with scopes" > select "Rovo MCP" > choose your scopes

  4. In LangSmith: Org Settings > MCP servers > Add server

    • URL: https://mcp.atlassian.com/v1/mcp

    • Auth: Static Headers

    • Header: Authorization: Basic <base64>

    • Compute base64: echo -n "<service-account-email>:<api-token>" | base64

The OAuth option is better for per-user access control; the API token option is simpler if you want a shared connection for the whole org.