I have a technical question for the community that I haven’t been able to find much information on, either here in the Q&A or elsewhere online.
I currently have a paid company instance of Jira and a free personal instance of Jira, and I wanted to connect both to Claude Desktop. At first, I didn’t give much thought to how I should connect them. I knew I could use MCP and create a custom server if needed, but then I noticed Claude’s new built-in Connectors feature. It made connecting to popular apps like Jira and Google Calendar much easier.
I connected our paid company Jira account using the Connectors integration, and it went smoothly and worked perfectly. Later, when I tried to connect my personal Jira instance, I realized I couldn’t install multiple Jira connections within the Connectors settings. So, I decided to use MCP for the personal instance instead. It took a little longer to set up, but I eventually got it working.
At first, I assumed only one instance should be active at a time to avoid confusion when prompting Claude. I practiced switching between them for a few days, but curiosity got the better of me, and I asked Claude if it could see both instances at the same time. It turns out it could. It worked fine for a while, but my personal MCP connection started having issues with basic function calls like get_issues. Claude tried to fix the problem, and it worked at first, but things got worse afterward.
So here’s my question: What’s the best way to connect multiple Jira instances to Claude and configure them to work together without conflicts? If the best solution is to manually enable one connection at a time, that’s fine. I just want to make sure I can access the same tools across each instance without issue.
Hi @Brian Griffin ,
Given you already have your company Jira working with Connectors, I suggest either way :)
1. Simplest one: Use only the Company Jira connection inside Claude for your main work. For personal Jira, either connect only when needed (and disconnect afterwards). Or you can leave it as MCP but mark clearly in prompts (so you avoid confusion).
2. More advanced way: Keep both active. Before each prompt to Claude, specify the instance (“Personal Jira”), and keep your prompts clear and project-key unique. Monitor the connection health for personal Jira token. If the personal instance continues to fail, you may need to re-authenticate or review its token/permissions.
I hope the links below are helpful for you:
Best,
Peter
Hi Brian - Welcome to the Atlassian Community!
I hope you were able to accomplish what you were trying to do. I am marking Peter's answer as Accepted. Please let us know if you have additional questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much @John Funk . And I hope you figured this problem out! Please let us know if you need any further inquiries.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The existing answer covers the mechanics well. The thing I'd add is that the failure pattern you saw (basic calls breaking, Claude's fixes making it worse) is usually not a connection bug, it's context bleed. Once Claude is holding two Jira instances in the same conversation, it starts guessing which one a comment or field update belongs to, and a wrong guess compounds because it then acts on that guess.
Two habits fixed this for me running multiple projects daily through one Jira instance, and they'd apply directly to your two-instance case. First, one instance per conversation, never mixed, even if technically both are reachable. Second, never let Claude write anything without showing you the proposed change first. That second rule is what actually catches the "which instance was that for" mistake before it hits a ticket, rather than after.
If you want to keep both live rather than switching connections manually, running two separate Claude conversations (one per instance) will be far more stable than one conversation juggling both, even though it's less convenient.
I wrote up the specific rules I use for this as a small kit after getting tired of re-explaining them every session, happy to share if it'd help: ai assisted PM kit - Jira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.