A Model-Context-Protocol(MCP) server to allow Claude desktop to create Jira tickets.
A Model-Context-Protocol(MCP) server to allow Claude desktop to create Jira tickets. The jira mcp integration mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.
A Model Context Protocol server for integrating JIRA with Claude. This tool allows Claude to create JIRA tickets directly within your conversations.
The JIRA MCP project is a Node.js/TypeScript application that provides a Model Context Protocol (MCP) server for integrating with JIRA and Zephyr. It allows AI assistants to interact with JIRA for project management and Zephyr for test management through a standardized protocol.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 8 environment variables: JIRA_HOST, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PROJECT_KEY, AUTO_CREATE_TEST_TICKETS, JIRA_ACCEPTANCE_CRITERIA_FIELD, JIRA_STORY_POINTS_FIELD, JIRA_EPIC_LINK_FIELD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by MankowskiNick; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"jira-mcp": {
"command": "node",
"args": ["/absolute/path/to/jira-mcp/build/index.js"],
"env": {
"JIRA_HOST": "your-site.atlassian.net",
"JIRA_USERNAME": "your-email@example.com",
"JIRA_API_TOKEN": "your_api_token",
"JIRA_PROJECT_KEY": "your_project_key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_HOST | Endpoint or connection string the server talks to. | Optional |
| JIRA_USERNAME | Configuration value read at startup. | Optional |
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_PROJECT_KEY | Credential the server authenticates with. | Yes |
| AUTO_CREATE_TEST_TICKETS | Configuration value read at startup. | Optional |
| JIRA_ACCEPTANCE_CRITERIA_FIELD | Configuration value read at startup. | Optional |
| JIRA_STORY_POINTS_FIELD | Configuration value read at startup. | Optional |
| JIRA_EPIC_LINK_FIELD | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.