mcp-server-atlassian-bitbucket and mcp-atlassian-server
These tools are complements because one provides an MCP server for Bitbucket while the other provides one for Jira and Confluence, enabling an AI assistant to interact with a broader set of Atlassian services.
About mcp-server-atlassian-bitbucket
aashari/mcp-server-atlassian-bitbucket
Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get, comment, search). Connects AI directly to version control workflows through the standard MCP interface.
Implements six generic REST tools (GET, POST, PUT, PATCH, DELETE, clone) that map directly to the Bitbucket Cloud 2.0 API, allowing LLMs to access any endpoint without hardcoded integrations. Supports both legacy App Passwords and Atlassian's newer scoped API tokens for authentication, with STDIO transport for seamless integration into Claude Desktop, Cursor AI, and other MCP-compatible clients. Includes JMESPath filtering to reduce token usage by transforming API responses before returning to the LLM.
About mcp-atlassian-server
phuc-nt/mcp-atlassian-server
MCP server connecting AI assistants with Jira & Confluence for smart project management.
Exposes 48 Jira and Confluence operations through standardized MCP resources (read-only) and tools (mutations), supporting advanced workflows like sprint management, version history, and dashboard automation. Built as a Node.js MCP server compatible with Cline, Claude Desktop, and Cursor, it authenticates via Atlassian API tokens and communicates through the Model Context Protocol. The architecture separates read operations (resources) from write operations (tools) for clear permission boundaries and integrates directly with Jira API v3 and Confluence API v2.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work