Jira MCP

Production FastMCP server for Jira Cloud (REST v3 / ADF) and Data Center (often REST v2 / plain text). This is a self-hosted adapter you run against your site. It is not Atlassian's hosted Rovo endpoint; it uses the same MCP ideas (Streamable HTTP, inbound auth, annotated tools, structured output).

Auth follows the same split used by Azure MCP and Atlassian Rovo:

1. Inbound — the MCP client authenticates to this server (HTTP only).

2. Outbound — this server authenticates to Jira with email + API token (Cloud Basic auth).

HTTP is fail-closed without MCP_JWKS_URI or MCP_JWT_SECRET.

Author: Clinton Follette.

Tools

Look up custom field ids with GET /rest/api/3/field after you create Source Ticket # and Customer Order # and put them on the create screen.

Related MCP server: Jira Issue MCP Server

Install (local STDIO)

{
  "mcpServers": {
    "jira": {
      "command": "mcp-jira",
      "env": {
        "JIRA_BASE_URL": "https://your-site.atlassian.net",
        "JIRA_EMAIL": "you@example.com",
        "JIRA_API_TOKEN": "<api-token>",
        "JIRA_SOURCE_TICKET_FIELD": "customfield_10001",
        "JIRA_CUSTOMER_ORDER_FIELD": "customfield_10002"
      }
    }
  }
}

Create a Cloud token at id.atlassian.com.

pip install .
mcp-jira

Remote HTTP

export MCP_TRANSPORT=http
export MCP_HOST=127.0.0.1
export MCP_PORT=8003
export MCP_JWKS_URI=https://login.example.com/.well-known/jwks.json
export MCP_JWT_ISSUER=https://login.example.com
export MCP_JWT_AUDIENCE=mcp-jira
mcp-jira

Endpoint: http://127.0.0.1:8003/mcp. Health: GET /health.

Outbound Jira configuration

Security

• HTTP without inbound JWT configuration refuses to boot.

• Issue and project keys are validated before they are placed in URLs.

• Custom field ids must start with customfield_ or they are ignored.

• mask_error_details is on.

See SECURITY.md.

License

MIT. Copyright (c) 2026 Clinton Follette.