MCP 2026-07-28 server for Jira and Confluence: sprints, boards, attachments, versions, calendars.
Mcp-atlassian-extended is an MCP integration. MCP 2026-07-28 server for Jira and Confluence: sprints, boards, attachments, versions, calendars.
The published pypi package is mcp-atlassian-extended, version 0.14.0. Its declared MCP transport is stdio.
The package declares JIRA_URL (required): Jira instance URL (e.g. https://your-domain.atlassian.net); JIRA_USERNAME: Jira Cloud account email. With JIRA_API_TOKEN this takes precedence over any token below.; JIRA_API_TOKEN: Jira Cloud API token, used with JIRA_USERNAME (basic auth); JIRA_PAT: Jira personal access token for Data Center (aliases: JIRA_PERSONAL_TOKEN, JIRA_TOKEN). Ignored when JIRA_USERNAME and JIRA_API_TOKEN are both set.; CONFLUENCE_URL: Confluence instance URL (optional, for Confluence tools). Cloud URLs usually need the /wiki suffix.; CONFLUENCE_USERNAME: Confluence Cloud account email. With CONFLUENCE_API_TOKEN this takes precedence over any token below.; CONFLUENCE_API_TOKEN: Confluence Cloud API token, used with CONFLUENCE_USERNAME (basic auth); CONFLUENCE_PAT: Confluence personal access token for Data Center (aliases: CONFLUENCE_PERSONAL_TOKEN, CONFLUENCE_TOKEN). Confluence tools also require the Team Calendars add-on.; ATLASSIAN_READ_ONLY: Restrict to read-only operations (true/false); ATLASSIAN_UPLOAD_DIR: Upload root for jira_upload_attachment; only files under it may be uploaded. Default: the working directory.; ATLASSIAN_DOWNLOAD_DIR: Directory jira_download_attachment writes into; created on first download. Default: ./atlassian-downloads/..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.14.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| JIRA_URL | Jira instance URL (e.g. https://your-domain.atlassian.net) | Yes |
| JIRA_USERNAME | Jira Cloud account email. With JIRA_API_TOKEN this takes precedence over any token below. | Check documentation |
| JIRA_API_TOKEN | Jira Cloud API token, used with JIRA_USERNAME (basic auth) | Check documentation |
| JIRA_PAT | Jira personal access token for Data Center (aliases: JIRA_PERSONAL_TOKEN, JIRA_TOKEN). Ignored when JIRA_USERNAME and JIRA_API_TOKEN are both set. | Check documentation |
| CONFLUENCE_URL | Confluence instance URL (optional, for Confluence tools). Cloud URLs usually need the /wiki suffix. | Check documentation |
| CONFLUENCE_USERNAME | Confluence Cloud account email. With CONFLUENCE_API_TOKEN this takes precedence over any token below. | Check documentation |
| CONFLUENCE_API_TOKEN | Confluence Cloud API token, used with CONFLUENCE_USERNAME (basic auth) | Check documentation |
| CONFLUENCE_PAT | Confluence personal access token for Data Center (aliases: CONFLUENCE_PERSONAL_TOKEN, CONFLUENCE_TOKEN). Confluence tools also require the Team Calendars add-on. | Check documentation |
| ATLASSIAN_READ_ONLY | Restrict to read-only operations (true/false) | Check documentation |
| ATLASSIAN_UPLOAD_DIR | Upload root for jira_upload_attachment; only files under it may be uploaded. Default: the working directory. | Check documentation |
| ATLASSIAN_DOWNLOAD_DIR | Directory jira_download_attachment writes into; created on first download. Default: ./atlassian-downloads/. | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.