Creativity · MCP — server

MCP Jira Server

The MCP Jira server lets LLM clients search and manipulate Jira issues through Atlassian's REST APIs. Atlassian runs an official hosted MCP endpoint for Jira Cloud (with OAuth-based auth) and there are community-maintained servers for Jira Data Center / Server. Typical uses: 'find all P0s assigned to me', 'file a bug for this stack trace', 'summarize this sprint backlog'.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: Python / TypeScript
Transports: stdio, http

Capabilities

Tools: search_issues (JQL), create_issue, update_issue, transition_issue, add_comment
Resources: project, issue, and sprint URIs
Auth: OAuth 2.0 (hosted) or API token + email (self-hosted)

Install

uvx mcp-atlassian

Configuration

{
  "mcpServers": {
    "jira": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "JIRA_URL": "https://your-org.atlassian.net",
        "JIRA_USERNAME": "[email protected]",
        "JIRA_API_TOKEN": "..."
      }
    }
  }
}

Frequently asked questions

Does Atlassian host an official MCP endpoint?

Yes. Atlassian provides a remote MCP endpoint for Jira Cloud (and Confluence Cloud) with OAuth-based auth. Add it to Claude Desktop or Claude.ai under Connectors.

What about Jira Data Center?

Use a community server like mcp-atlassian running locally. It speaks to your Data Center URL via REST and authenticates with a personal access token.

Can the server create or close tickets?

Yes, write tools exist. Because Jira workflow changes are audit-logged, confirm tool approvals in your client settings and prefer a dedicated bot user so actions are attributable.

Sources

Atlassian Remote MCP — accessed 2026-04-20
mcp-atlassian GitHub — accessed 2026-04-20