Jira MCP Server
Provides tools to create Jira issues and list available issue types for a project using the Jira Cloud API.
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 Server create a task in project PROJ: update API documentation"
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.
Jira MCP Server
MCP (Model Context Protocol) server for Jira Cloud API integration. Create issues and list issue types using Basic Auth (email + API token).
Features
jira_create_issue – Create a new Jira issue with project, summary, and issue type
jira_list_issue_types – List available issue types for a project
Related MCP server: mcp-jira
Prerequisites
Node.js 24+
Jira Cloud site
Setup
Clone and install
cd jira_mcp npm installConfigure environment
Copy
.env.exampleto.envand fill in your values:cp .env.example .envJIRA_BASE_URL=https://your-domain.atlassian.net JIRA_EMAIL=user@example.com JIRA_API_TOKEN=your_api_token_hereBuild
npm run build
Usage
Run the server
npm startOr with env vars inline:
JIRA_BASE_URL=https://your-domain.atlassian.net JIRA_EMAIL=you@example.com JIRA_API_TOKEN=xxx npm startThe server runs via stdio and is intended to be used as a subprocess by MCP clients (e.g. Cursor, Claude Desktop).
Cursor configuration
Add to your Cursor MCP config (e.g. ~/.cursor/mcp.json):
{
"mcpServers": {
"jira": {
"command": "node",
"args": ["/path/to/jira_mcp/dist/index.js"],
"env": {
"JIRA_BASE_URL": "https://your-domain.atlassian.net",
"JIRA_EMAIL": "your-email@example.com",
"JIRA_API_TOKEN": "your-api-token"
}
}
}
}Tools
jira_list_issue_types
List issue types (Bug, Task, Story, etc.) for a project.
Parameter | Type | Required | Description |
project_key | string | Yes | Jira project key (e.g. PROJ) |
response_format | string | No |
|
jira_create_issue
Create a new Jira issue.
Parameter | Type | Required | Description |
project_key | string | Yes | Jira project key |
summary | string | Yes | Issue title |
issue_type | string | Yes | Issue type name (e.g. Bug, Task) or ID |
description | string | No | Issue description |
response_format | string | No |
|
Testing Without Cursor
The best way to test the MCP server interactively is with MCP Inspector, a web UI for exercising tools, resources, and prompts.
Build the project (if not already done):
npm run buildRun MCP Inspector with your server. With a
.envfile in the project root, the server loads it automatically:npm run inspectorOr run directly (env from
.envis loaded by the server):npx @modelcontextprotocol/inspector node dist/index.jsTo pass env vars explicitly instead:
npx @modelcontextprotocol/inspector \ -e JIRA_BASE_URL=https://your-domain.atlassian.net \ -e JIRA_EMAIL=you@example.com \ -e JIRA_API_TOKEN=your-token \ node dist/index.jsOpen the Inspector in your browser (typically
http://localhost:6274).Test tools – Use the Tools tab to call
jira_list_issue_typesandjira_create_issuewith sample inputs.
The Inspector runs your server as a subprocess and connects via stdio, so it behaves like a real MCP client.
Development
# Run with auto-reload
npm run dev
# Run all tests (unit + integration)
npm test
# Run tests with coverage
npm run test:coverage
# Run integration tests only (spawns MCP server + mock Jira)
npm run test:integration
# Lint code
npm run lint
npm run lint:fix
# Format code
npm run format
npm run format:checkPre-commit hooks (Husky)
On each git commit, Husky runs lint and Prettier on staged files. If there are errors, the commit is blocked with a message:
❌ Commit blocked: Fix the lint or Prettier errors above.
Tips: npm run lint:fix | npm run formatTo bypass (use sparingly): git commit --no-verify or HUSKY=0 git commit
CI
GitHub Actions runs on pull requests to main/master with separate stages on Node.js 24.x:
Unit Tests –
npm run test:unit(90% coverage enforced)Integration Tests –
npm run test:integration(MCP server + mock Jira)Lint & Format – ESLint and Prettier checks
Security Audit –
npm audit(fails on moderate+ vulnerabilities)CodeQL – Static security analysis (JavaScript/TypeScript)
Dependency Review – Checks for vulnerable deps in PRs
Dependabot is configured for weekly dependency updates (.github/dependabot.yml).
To block merges until PRs pass, enable branch protection in GitHub: Settings → Branches → Add rule → Require status checks to pass before merging.
API Reference
License
MIT
Available Tools
2 toolsjira_create_issueCreate Jira IssueA
Create a new Jira issue in a project.
Creates an issue with the given project, summary, and issue type. Use jira_list_issue_types to discover valid issue types for a project.
Args:
project_key (string): Jira project key (e.g. PROJ)
summary (string): Issue title (required)
issue_type (string): Issue type name (e.g. Bug, Task) or numeric ID
description (string, optional): Issue description
response_format ('markdown' | 'json'): Output format (default: 'markdown')
Returns: For JSON: { "key": string, "id": string, "self": string } For Markdown: Summary with issue key and link
Examples:
Create a bug: project_key="PROJ", summary="Login fails", issue_type="Bug"
Create a task: project_key="DEMO", summary="Review docs", issue_type="Task"
Error Handling:
401: Check JIRA_EMAIL and JIRA_API_TOKEN
403: No create permission in project
404: Project or issue type not found
422: Validation error (e.g. missing required fields)
Inputs: summary (required), issue_type (required), project_key (required), description, +1 more.
jira_list_issue_typesList Jira Issue TypesARead-onlyIdempotent
List issue types available for a Jira project.
Use this tool to discover which issue types (e.g. Bug, Task, Story) can be used when creating issues in a project. Returns id, name, and description for each type.
Args:
project_key (string): Jira project key (e.g. PROJ, DEMO)
response_format ('markdown' | 'json'): Output format (default: 'markdown')
Returns: For JSON: { "issue_types": [{ "id": string, "name": string, "description": string }] } For Markdown: Formatted list of issue types
Examples:
"What issue types can I create in project PROJ?" -> project_key="PROJ"
Use before jira_create_issue to get valid issue_type values
Error Handling:
401: Check JIRA_EMAIL and JIRA_API_TOKEN
403: Insufficient permissions for the project
404: Project not found
Inputs: project_key (required), response_format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools are completely distinct: one lists issue types for discovery, the other creates an issue. There is no overlap or ambiguity between them.
Both tools follow the same 'jira_verb_noun' pattern (jira_list_issue_types, jira_create_issue), making the naming predictable and consistent.
With exactly 2 tools, the server sits in the 'borderline thin' range. While the scope is clear, a Jira server typically needs more tools to be useful.
The tools cover only creation and issue-type lookup. Missing get, update, delete, search, and project listing means agents cannot verify or manage issues, leaving significant workflow gaps.
Maintenance
Related MCP Connectors
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
List, view, create, edit, delete, comment on, and see the history of Laraue Boards issues.
Read projects, tasks, comments, people and time entries; create tasks and comments in ProofHub.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Jira issues, projects, and comments via API Key. Supports operations like creating, updating, searching, transitioning issues, and managing projects.708 npmMIT
- AlicenseAqualityDmaintenanceEnables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.931 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables creating, fetching, and updating Jira issues via the REST API with support for ADF descriptions and common fields like priority, labels, and issue types.1,667 npm2Apache 2.0