MCP Jira Stdio vs Jira MCP
A side-by-side look at the MCP Jira Stdio and Jira MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Jira Stdio for product management work as a local process; choose Jira MCP for product management. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Jira Stdio when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN. - You want tools like
jira_get_visible_projects, jira_get_issue, jira_search_issues.
Choose Jira MCP when
- You need dedicated capabilities in the Product Management domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
ATLASSIAN_HOST, ATLASSIAN_EMAIL, ATLASSIAN_TOKEN, ENABLED_TOOLS. - You want tools like
jira_get_issue, jira_create_issue, jira_create_child_issue.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 67/100 · Great | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | API key required |
| Pricing | Not declared | Free |
| Required env vars | JIRA_BASE_URLJIRA_EMAILJIRA_API_TOKEN | ATLASSIAN_HOSTATLASSIAN_EMAILATLASSIAN_TOKENENABLED_TOOLS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 96 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 23 | 21 |
| Full listing | View MCP Jira Stdio | View Jira MCP |
Tools & capabilities
MCP Jira Stdio tools 23
jira_get_visible_projectsRetrieves all projects accessible to the authenticated user. Returns project keys, names, descriptions, and basic metadata.jira_get_issueRetrieve details for a specific Jira issue by key or URL. Use this when the user mentions an issue like "PAYWALL-943" or pastes a Jira link (e.g., https://your.atlassian.net/browse/PAYWALL-943). Returns status, assignee, priority, project, type, labels, components, timestamps, and description.jira_search_issuesSearch for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "project = PROJECT AND status = Open", "assignee = currentUser()". For pagination, use nextPageToken from previous response.jira_get_my_issuesRetrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. For pagination, use nextPageToken from previous response.jira_get_issue_typesRetrieves available issue types. Can get global issue types or project-specific issue types including regular issues and subtasks (Bug, Story, Task, Epic, etc.).jira_get_usersSearch for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination.jira_get_prioritiesRetrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions.jira_get_statusesRetrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information.jira_get_project_infoRetrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list.jira_get_create_metaRetrieves create metadata for a project, showing all available fields (including custom fields) for creating issues. Shows required vs optional fields, field types, and allowed values. Use this before creating issues to discover what fields are needed.jira_get_custom_fieldsRetrieves all custom fields available in Jira. Shows custom field names, IDs (e.g., customfield_10071), and types. Useful for discovering what custom fields exist and their identifiers.jira_get_commentsRetrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Supports pagination for issues with many comments.- +11 more on the listing page
Jira MCP tools 21
jira_get_issueRetrieve detailed information about a specific issue including status, assignee, description, subtasks, and available transitionsjira_create_issueCreate a new issue with specified details (returns key, ID, and URL)jira_create_child_issueCreate a child issue (sub-task) linked to a parent issuejira_update_issueModify an existing issue's details (supports partial updates)jira_list_issue_typesList all available issue types in a project with their IDs, names, and descriptionsjira_search_issueSearch for issues using JQL (Jira Query Language) with customizable fields and expand optionsjira_list_sprintsList all active and future sprints for a specific board or projectjira_get_sprintRetrieve detailed information about a specific sprint by its IDjira_get_active_sprintGet the currently active sprint for a given board or projectjira_search_sprint_by_nameSearch for sprints by name with exact or partial matchingjira_list_statusesRetrieve all available issue status IDs and their names for a projectjira_transition_issueTransition an issue through its workflow using a valid transition ID- +9 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Jira Stdio
{
"mcpServers": {
"mcp-jira-stdio": {
"command": "npx",
"args": [
"-y",
"mcp-jira-stdio@latest"
],
"env": {
"JIRA_BASE_URL": "YOUR_JIRA_BASE_URL_HERE",
"JIRA_EMAIL": "YOUR_JIRA_EMAIL_HERE",
"JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE"
}
}
}
}
Jira MCP
No confirmed install command for Jira MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Jira Stdio is categorized under Product Management and uses a local stdio subprocess. Jira MCP belongs to Product Management and uses an install path we have not confirmed yet. Pick MCP Jira Stdio for product management work and Jira MCP for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Jira MCP has no confirmed install command yet — follow its own setup instructions.
MCP Jira Stdio has no declared pricing — check the project's own site. Auth: api key required. Jira MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-jira-stdio and nguyenvanduocit-jira-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Jira Stdio has a quality signal of 67/100 (Great) with 2 views, 0 installs and 14 GitHub stars. Jira MCP has 52/100 (Good) with 4 views, 0 installs and 96 GitHub stars.