Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

MCP Atlassian

PyPI Version PyPI - Downloads PePy - Total Downloads Run Tests License Docs

Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.

https://github.com/user-attachments/assets/35303504-14c6-4ae4-913b-7c25ea511c3e

Confluence Demo

https://github.com/user-attachments/assets/7fe9c488-ad0c-4876-9b54-120b666bb785

Quick Start

1. Get Your API Token

Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a token.

For Server/Data Center, use a Personal Access Token instead. See Authentication.

2. Configure Your IDE

Add to your Claude Desktop or Cursor MCP configuration:

{
  "mcpServers": {
    "bcs-mcp-atlassian": {
      "command": "uvx",
      "args": ["bcs-mcp-atlassian"],
      "env": {
        "JIRA_URL": "https://your-company.atlassian.net",
        "JIRA_USERNAME": "your.email@company.com",
        "JIRA_API_TOKEN": "your_api_token",
        "CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "your.email@company.com",
        "CONFLUENCE_API_TOKEN": "your_api_token"
      }
    }
  }
}

Server/Data Center users: Use JIRA_PERSONAL_TOKEN instead of JIRA_USERNAME + JIRA_API_TOKEN. See Authentication for details.

Optional — content masking: To send Jira/Confluence text content through an external mask/verification service before returning it to the client, set CONTENT_MASK_SERVICE_URL to the service endpoint (e.g. https://apis.tusvc.bcs.ru/mai-ms-masking-it-proxy/mask/chat). If unset, content is returned as-is.

Optional — log file: To write server logs to a file (e.g. to view them in Cursor when the MCP client panel does not show server stderr), set MCP_LOG_FILE to a file path (e.g. bcs-mcp-atlassian.log). Logs are appended to the file in UTF-8.

Running with local code (e.g. in Cursor): To avoid "program not found" when Cursor spawns the process (wrong working directory or uv not in PATH), use the wrapper script as command with the full path to this repo:

"bcs-mcp-atlassian": {
  "command": "C:\\Users\\Anton\\Downloads\\atlassian\\bcs-mcp-atlassian-bcs\\run-bcs-mcp-atlassian.bat",
  "args": [],
  "env": {
    "JIRA_URL": "https://jira.bcs.ru",
    "JIRA_PERSONAL_TOKEN": "<your-token>",
    "CONFLUENCE_URL": "https://confluence.bcs.ru",
    "CONFLUENCE_PERSONAL_TOKEN": "<your-token>",
    "CONTENT_MASK_SERVICE_URL": "https://apis.tusvc.bcs.ru/mai-ms-masking-it-proxy/mask/chat"
  }
}

Replace the path with your actual clone path. The script run-bcs-mcp-atlassian.bat switches to the project directory and runs uv run bcs-mcp-atlassian there. If your workspace root is this folder and uv is in PATH, you can instead use "command": "uv" and "args": ["run", "bcs-mcp-atlassian"].

3. Start Using

Ask your AI assistant to:

  • "Find issues assigned to me in PROJ project"
  • "Search Confluence for onboarding docs"
  • "Create a bug ticket for the login issue"
  • "Update the status of PROJ-123 to Done"

Documentation

Full documentation is available at bcs-mcp-atlassian.soomiles.com.

Documentation is also available in llms.txt format, which LLMs can consume easily:

Topic Description
Installation uvx, Docker, pip, from source
Authentication API tokens, PAT, OAuth 2.0
Configuration IDE setup, environment variables
HTTP Transport SSE, streamable-http, multi-user
Tools Reference All Jira & Confluence tools
Troubleshooting Common issues & debugging

Compatibility

Product Deployment Support
Confluence Cloud Fully supported
Confluence Server/Data Center Supported (v6.0+)
Jira Cloud Fully supported
Jira Server/Data Center Supported (v8.14+)

Key Tools

Jira Confluence
jira_search - Search with JQL confluence_search - Search with CQL
jira_get_issue - Get issue details confluence_get_page - Get page content
jira_create_issue - Create issues confluence_create_page - Create pages
jira_update_issue - Update issues confluence_update_page - Update pages
jira_transition_issue - Change status confluence_add_comment - Add comments

72 tools total — See Tools Reference for the complete list.

Security

Never share API tokens. Keep .env files secure. See SECURITY.md.

Contributing

See CONTRIBUTING.md for development setup.

License

MIT - See LICENSE. Not an official Atlassian product.

Metadata

Release files for bcs-mcp-atlassian 0.0.1.dev556

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bcs-mcp-atlassian 0.0.1.dev556
File Size Uploaded Provenance Actions
bcs_mcp_atlassian-0.0.1.dev556.tar.gz 820.4 kB Without provenance Details for bcs_mcp_atlassian-0.0.1.dev556.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bcs-mcp-atlassian 0.0.1.dev556
File Interpreter ABI Platform Actions
bcs_mcp_atlassian-0.0.1.dev556-py3-none-any.whl Python 3 none any Details for bcs_mcp_atlassian-0.0.1.dev556-py3-none-any.whl

Total release size: 1.1 MB

Release files / bcs_mcp_atlassian-0.0.1.dev556.tar.gz

Download URL bcs_mcp_atlassian-0.0.1.dev556.tar.gz
Size 820.4 kB
Tags Source
SHA-256 checksum
How to use checksums
da7e6ac8ffaa3d778bec59a549e867ba2f8e3038b28e6a2534ae37b4eb4d44e2
BLAKE2b-256 checksum
How to use checksums
ac23b61d64416c8baae9500a88ee890fb8499711ed8337fc7bd73dc55babc4f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.9.8

Release files / bcs_mcp_atlassian-0.0.1.dev556-py3-none-any.whl

Download URL bcs_mcp_atlassian-0.0.1.dev556-py3-none-any.whl
Size 287.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
593b4ef1ffeec48e6a24f2ffad510cc380d249181068da2e82d193ceb973116b
BLAKE2b-256 checksum
How to use checksums
d66152fed2ec5970d0cbf0d05323388715368b045350b83515b4627d5bf08dd0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.9.8

Security for bcs-mcp-atlassian 0.0.1.dev556

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page