atlassian-multi-mcp
Provides account management tools for multiple Atlassian sites, enabling auto-routing based on issue keys or URLs.
Allows managing Confluence pages, spaces, comments, and searching via CQL in multiple Confluence workspaces.
Allows managing Jira issues, comments, transitions, worklogs, links, and searching via JQL in multiple Jira workspaces.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
atlassian-multi-mcp
Multi-account Atlassian MCP server for Claude Code. Supports multiple Jira/Confluence workspaces simultaneously with automatic account routing by URL or issue key.
Features
Multiple accounts — configure as many Atlassian sites as needed
Auto-routing — detects the correct account from issue key prefix (
RES-123→ radekwork), full URL, or aliasFull Jira coverage — get/create/edit issues, comments, transitions, worklogs, links, search (JQL)
Full Confluence coverage — pages, spaces, comments, search (CQL)
Account management tools — add/remove/test accounts from within Claude
Related MCP server: Cloud Jira MCP
Installation
Via npx (recommended)
npx atlassian-multi-mcpGlobal install
npm install -g atlassian-multi-mcpClaude Code Setup
Add to your ~/.claude/settings.json under mcpServers:
{
"mcpServers": {
"atlassian": {
"command": "npx",
"args": ["-y", "atlassian-multi-mcp"]
}
}
}Or as a Claude Code plugin:
claude plugin install ntlongctt/atlassian-multi-mcpConfigure Accounts
After installing, use the add_atlassian_account tool in Claude:
add_atlassian_account:
alias: "radekwork"
site: "radekwork.atlassian.net"
email: "you@example.com"
token: "ATATT..."
projectPrefixes: "RES,RS"
isDefault: falseOr edit ~/.atlassian-accounts.json directly:
{
"accounts": [
{
"alias": "doneitbetter",
"site": "doneitbetter.atlassian.net",
"email": "you@doneitbetter.com",
"token": "ATATT...",
"projectPrefixes": ["DIB"],
"isDefault": true
},
{
"alias": "radekwork",
"site": "radekwork.atlassian.net",
"email": "you@radek.com",
"token": "ATATT...",
"projectPrefixes": ["RES", "RS", "SHIELD"]
}
]
}Get API tokens at: https://id.atlassian.com/manage-profile/security/api-tokens
Account Resolution
The server resolves which account to use in this order:
Full URL —
https://radekwork.atlassian.net/browse/RES-123→ radekwork accountIssue key —
RES-123→ lookupRESinprojectPrefixes→ radekwork accountAlias —
"radekwork"→ exact alias matchPartial site —
"radek"→ partial hostname matchDefault account —
isDefault: truein configSingle account — use it if only one configured
Available Tools
Account Management
Tool | Description |
| List all configured accounts |
| Add a new account (tests connection) |
| Remove an account |
| Set default account |
| Test credentials |
| List all sites (compatible with built-in Atlassian MCP) |
Jira
Tool | Description |
| Get issue by key or URL |
| Search with JQL |
| Create issue |
| Edit issue fields |
| Add comment |
| Get workflow transitions |
| Move to new status |
| List projects |
| Get issue types |
| Get fields for issue type |
| Search users |
| Get link types |
| Link two issues |
| Log time |
| Get external links |
| Current user info |
Confluence
Tool | Description |
| Get page by ID |
| Create page |
| Update page |
| Search with CQL |
| List spaces |
| List pages in space |
| Get child pages |
| Get comments |
| Add comment |
| Get inline comments |
| Add inline comment |
| Get comment replies |
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP for Google Workspace, Atlassian and Notion: one OAuth, per-user accounts, write access.
Autotask MCP server for ChatGPT, Claude and any AI agent: search tickets, create ticket, update ticket, add ticket note, log time entry and find company in your own Autotask account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Autotask yourself; Cotlet does not store your password and you need no Autotask API key. About the official Autotask API: Autotask has a full REST API, and Kaseya publishes an official Autotask MCP server that is still in alpha (checked 6 Nov 2026). Both run as an API-only user with an integration code, set up by an admin, and the MCP server supports Claude only. Setup and FAQ: https://cotlet.dev/integrations/autotask-api-mcp-server
Persistent memory and shared context across compatible AI assistants, with account-scoped OAuth.
AppFlowy MCP server for ChatGPT, Claude and any AI agent: list workspaces, read page tree, list database rows, create database row, update database row, create page, restore from trash and share page in your own AppFlowy account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to AppFlowy yourself; Cotlet does not store your password and you need no AppFlowy API key. About the official AppFlowy API: AppFlowy Cloud has a documented REST API for workspaces, the folder tree and database rows, but no hosted MCP server (checked 25 Oct 2026). The official MCP service is an optional part of the commercial self-hosted edition. Setup and FAQ: https://cotlet.dev/integrations/appflowy-api-mcp-server
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceSupercharge your AI assistant with seamless Jira integration. Enables AI assistants like GitHub Copilot and Claude to interact with your Jira Cloud instance.874 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables management of multiple Jira Cloud instances through MCP, including workspace linking, issue creation and editing, workflow transitions, attachment retrieval, and administration via a web interface.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Jira and Confluence on Atlassian Cloud, supporting issue search, creation, updates, transitions, project listing, content search, page management, and comments.148 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables one agent session to work across many Jira Cloud sites at once, routing each request by issue-key prefix so users can fetch and search issues, manage comments, and download or upload attachments directly to disk instead of shuffling base64 through chat context.1MIT