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.

Cloud v3Data Center v2OAuth + PKCE
terminal

$ jira-mcp setup

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

Deployment (cloud/server): cloud

Jira email: you@acme.com

Jira API token: ********

Ready. Connect your MCP host.

01

Native MCP

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

02

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.

03

Built to be trusted

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

01 / Local setup

Connect in under a minute.

Download a release or build from source, then let the setup wizard create a local configuration with restrictive permissions. 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 .

# configure
./jira-mcp setup

# 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
# required environment
JIRA_MCP_PUBLIC_URL=https://mcp.example.com
JIRA_MCP_ATLASSIAN_CLIENT_ID=...
JIRA_MCP_ATLASSIAN_CLIENT_SECRET=...
JIRA_MCP_ENCRYPTION_KEY=...
VALKEY_URL=rediss://...

# run anywhere with Docker
docker build -t jira-mcp .
docker run --env-file .env -p 8080:8080 jira-mcp