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)
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/**)In LangSmith: Org Settings > MCP servers > Add server
URL:
https://mcp.atlassian.com/v1/mcpAuth: OAuth 2.1 (Auto)
Click Connect and approve Jira/Confluence/Compass access
Each end user will need to complete the OAuth flow once in their Fleet session
Option 2: API token with shared service account
In Atlassian admin > Rovo > Rovo MCP server > Authentication, enable "Allow API token authentication"
Create a service account user with access to the relevant Jira projects and Confluence spaces
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
In LangSmith: Org Settings > MCP servers > Add server
URL:
https://mcp.atlassian.com/v1/mcpAuth: 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.