Provides tools to retrieve issue details and create issues in Jira, supporting both Jira Cloud and Jira Data Center.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Jira MCP show me the details for Jira issue PROJ-123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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:
Inbound — the MCP client authenticates to this server (HTTP only).
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.
Tool | Access | Notes |
| read | Key, status, summary, Source Ticket #, Customer Order #. |
| write | Project, issue type, summary, description. Hidden when |
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
{
"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-jiraexport 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-jiraEndpoint: http://127.0.0.1:8003/mcp. Health: GET /health.
Variable | Required | Purpose |
| yes | Site origin |
| yes | Cloud account |
| yes | API token |
| no | Default |
| no |
|
| no | Default |
| for close-loop |
|
| for T2 |
|
| no | Hide |
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.
MIT. Copyright (c) 2026 Clinton Follette.
Create a Jira work item. Cloud v3 descriptions are sent as Atlassian Document Format. Source Ticket # and Customer Order # are written when those customfield ids are configured.
Inputs: summary (required), project_key (required), labels, issue_type, +3 more. Returns: id, key, self_url
Read a Jira issue key, status, summary, Source Ticket #, and Customer Order #.
Inputs: key (required). Returns: key, status, summary, source_ticket, +1 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Scored across 2 tools
get_issue and create_issue have unambiguous, non-overlapping purposes — one reads, one writes. An agent can select correctly without hesitation.
Both tools follow a clean, predictable verb_noun snake_case pattern (get_issue, create_issue), consistent with common MCP conventions.
Only 2 tools for a server branded as a general 'Jira MCP' is thin; it covers just a narrow read/create slice of the Jira domain and leaves the set feeling minimally scoped.
Create and get are present but there is no update, delete, search, transition, or comment operation, so agents hit dead ends for common Jira workflows. The narrow customfield focus partially excuses the gap but not fully.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
MCP server for GLPI: tickets, ITIL, assets, knowledge base. GLPI 10/11. Not affiliated with Teclib'.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.