What it does & operational scope
Atlassian MCP Server connects developer assistants to enterprise Jira instances and Confluence workspaces over standard input and output. It enables agents to search Jira backlogs via JQL, update issue workflows, attach worklogs, and read or edit Confluence documentation pages through standard REST API endpoints.
Atlassian MCP Server is an open-source Model Context Protocol server licensed under MIT that connects AI assistants to Jira issues and Confluence wiki spaces over stdio.
Your AI coding agent requires live access to Atlassian Jira & Confluence tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "atlassian": { "command": "uvx", "args": ["mcp-atlassian"], "env": { "JIRA_URL": "https://company.atlassian.net", "JIRA_USERNAME": "user@company.com", "JIRA_API_TOKEN": "<YOUR_TOKEN>" } } }}Exposed tool endpoints & primitives
Discovered MCP Tools
5 Tools Readyjira_get_issue🟢 Read-Only (Safe)Fetch Jira ticket summary, status, description, and assignees by issue key
jira_search_jql🟢 Read-Only (Safe)Execute JQL search query returning matching Jira issue keys and metadata
jira_create_issue🟡 State MutationCreate a new Jira issue under a project with issue type, summary, and fields
confluence_get_page🟢 Read-Only (Safe)Read Confluence document body, space key, and version metadata by title or ID
confluence_search🟢 Read-Only (Safe)Search Confluence spaces and wiki content using CQL text queries
Scopes, secret storage, and sandbox boundaries
Run Atlassian Jira & Confluence MCP Server with scoped environment tokens. Never run under root and restrict network ingress.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Atlassian Jira & Confluence MCP Server from the last 7 days"jira_get_issue({ query: "Atlassian Jira & Confluence MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Atlassian Jira & Confluence MCP Server"jira_get_issue_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Unifies Jira project boards and Confluence documentation under a single server.
+ Supports advanced JQL queries for filtering issues across large organizations.
+ Allows automated updating of internal wiki specs following code refactors.
− Complex enterprise Jira instances with mandatory custom fields or restrictive security schemes trigger obscure 400 Bad Request errors.
− Confluence document trees formatted in Atlassian Document Format (ADF) consume heavy token allowances when converted to JSON payloads.
Side-by-side rival comparisons
Compare Atlassian Jira & Confluence MCP Server vs Linear MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 1,4 "method": "tools/call",5 "params": {6 "name": "inspect",7 "arguments": {}8 }9}
