By Goptin · Updated 2026-11-05
Jira sites from different companies in one Claude session
Contractors and people with two jobs often have two Jira sites under two different Atlassian accounts — you@company-a.com on one, you@client-b.com on the other. You want Claude to see both: "what's assigned to me this sprint, everywhere?"
Here is what the official Atlassian server covers, where it stops, and how to get both sites into one session.
What the Atlassian MCP server covers
Atlassian's Rovo MCP server signs in with one Atlassian account and works with the sites that account can access. If both Jira sites sit under the same login, it is the simplest choice.
Separate companies usually mean separate Atlassian accounts and organizations. Then one sign-in only reaches one side, and switching means re-authenticating. Connecting several sites in one session is an open request in Atlassian's tracker (ECO-1259).
Your options
1. Register the Atlassian server twice (Claude Code). Add it as jira-a and jira-b and sign each copy in with a different account. It works, but tools are duplicated, each login has to stay alive, and Claude has to guess which copy to call.
2. One MCP server that holds every account. Goptin connects each Atlassian account once and exposes one tool set — list_tickets, get_ticket, comment_ticket, update_ticket — where each call names the account. The same server carries Slack, Teams, Google Chat and ClickUp, so "post my Jira progress in the client's Slack" is one prompt.
Set it up with Goptin
- 1Connect each Atlassian accountIn Goptin → Connections, connect Jira with the first Atlassian account — every site that account can access is added. Then connect again with the second account.
- 2Group them into workspaces (optional)Put each company's Jira and chat accounts into a workspace like "Job A" and "Job B", so prompts can simply say "job B".
- 3Add the server to Claude Code or CursorCreate a token in Settings → Integrations, then add the server. Configs for Cursor and other clients are on the MCP page.
claude mcp add --transport http goptin https://app.goptin.com/mcp --scope user --header "Authorization: Bearer goptin_…"
- 4Ask across both sites"List my open Jira tickets at job A and job B for this sprint, sorted by priority."
Atlassian MCP vs. registered twice vs. Goptin
| Atlassian MCP | Atlassian MCP registered twice | Goptin MCP | |
|---|---|---|---|
| Sites under one Atlassian login | Yes | Yes | Yes |
| Sites under different Atlassian accounts | Re-authenticate to switch | One account per copy | All at once |
| Confluence | Yes | Yes | No — Jira and ClickUp tickets only |
| Chat apps in the same server | — | — | Slack, Teams, Google Chat |
| Clients | Most MCP clients | Claude Code | Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Windsurf |
FAQ
Can Claude access two Jira Cloud sites at once?
If both sites are under the same Atlassian login, the Atlassian MCP server already can. For sites under different Atlassian accounts, use a server that holds several accounts — Goptin connects each account once and every tool takes an account argument.
Does Goptin support Confluence?
Not yet. It covers Jira and ClickUp tickets plus chat apps. Keep the Atlassian server for Confluence if you need it — both can be registered side by side.
Will Claude change tickets without asking?
No. Claude Code asks for permission before every tool call that comments on or moves a ticket, and the server tells the model to show you the change first.
How much does it cost?
The MCP server is included in every Goptin plan, including the 14-day free trial — no card required.
No card needed. Revoke the token any time in Settings → Integrations.