Enables AI assistants to programmatically manage Jira issues through the Jira REST API.
Jira Integration MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Enables AI assistants to programmatically manage Jira issues through the Jira REST API.
A Model Context Protocol server that provides integration with Jira's REST API, allowing AI assistants to manage Jira issues programmatically.
Once Jira Integration is connected, these are the calls the assistant has available:
Prerequisites — 1. A Jira account with API access 2. Jira API token (can be generated from [Atlassian AccountInstallation — The Installation tool exposed by this serverConfiguration — 1. Create a .jira-config.json file in your working directory:create_issue — The create_issue tool exposed by this serverlist_issues — The list_issues tool exposed by this serverupdate_issue — The update_issue tool exposed by this serverget_issue — The get_issue tool exposed by this serverdelete_issue — The delete_issue tool exposed by this serveradd_comment — The add_comment tool exposed by this serverYou will need 5 environment variables: JIRA_EMAIL, JIRA_API_TOKEN, JIRA_DOMAIN, YOUR_PROJECT_KEY, YOUR_OTHER_PROJECT_KEY. 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.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
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. Jira Integration's toolset — Prerequisites, Installation, Configuration and 6 more — is a fair guide to whether it matches your workflow. It is maintained by 1broseidon; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Jira Integration's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | 1. A Jira account with API access 2. Jira API token (can be generated from [Atlassian Account Settings](https://id.atlassian.com/manage-profile/security/api-tokens)) |
| Installation | The Installation tool exposed by this server. |
| Configuration | 1. Create a .jira-config.json file in your working directory: |
| create_issue | The create_issue tool exposed by this server. |
| list_issues | The list_issues tool exposed by this server. |
| update_issue | The update_issue tool exposed by this server. |
| get_issue | The get_issue tool exposed by this server. |
| delete_issue | The delete_issue tool exposed by this server. |
| add_comment | The add_comment tool exposed by this server. |
{
"mcpServers": {
"jira": {
"command": "node",
"args": ["/path/to/jira-server/build/index.js"],
"env": {
"JIRA_EMAIL": "your-email@example.com",
"JIRA_API_TOKEN": "your-api-token",
"JIRA_DOMAIN": "your-domain"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_EMAIL | Configuration value read at startup. | Optional |
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_DOMAIN | Configuration value read at startup. | Optional |
| YOUR_PROJECT_KEY | Credential the server authenticates with. | Yes |
| YOUR_OTHER_PROJECT_KEY | Credential the server authenticates with. | Yes |
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.