Open-source MCP server

Give your AI a direct line to Jira.

Search, create, update and move issues from any MCP host. Runs locally over stdio — or self-hosted over HTTP, where you own the infrastructure and the credentials.

Get started View source

Cloud v3Data Center v2OAuth + PKCE

terminal

$ jira-mcp setup

Jira site URL: https://acme.atlassian.net

Deployment: cloud

Atlassian account email: you@acme.com

Cloud API token (input hidden): ********

✓ Saved locally. Choose your AI client.

Restart the client, then run jira-mcp doctor if needed.

█

Native MCP

Official Go SDK and protocol-level tests. Works with OpenCode and any compatible host.

Self-hosted by design

Stdio for local use. Need to share an instance with a team? Deploy your own server with Atlassian OAuth — no hosted service, your infrastructure, your credentials.

Built to be trusted

PKCE, encrypted tokens, isolated users, Valkey sessions and contract-tested Jira APIs.

01 / Local setup

Connect in under a minute.

For Jira Cloud, create an API token at Atlassian account security. The wizard hides token input, saves credentials in a user-only local config, and detects AI clients to configure. Add another client later with jira-mcp install-mcp; add Jira usage guidance to your project with jira-mcp install-instructions. Want a shared instance? Deploy your own — the repository's deployment guides cover self-hosting on Railway or any environment.

# build
go build -o jira-mcp ./cmd/jira-mcp

# configure
./jira-mcp setup

# register another client later
./jira-mcp install-mcp

# run over stdio
./jira-mcp

02 / Self-hosted HTTP

Run your own shared instance.

For teams, deploy the same binary on infrastructure you control. You provide the public URL, an Atlassian OAuth app, Valkey, and the encryption key. There is no hosted Jira MCP service behind this project.

Register /oauth/callback as the OAuth callback, expose /mcp, and keep all secrets in your platform's environment variables.

Read the self-hosting guide