Jira MCP vs RoadRaven
A side-by-side look at the Jira MCP and RoadRaven MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jira MCP for product management work; choose RoadRaven for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose RoadRaven when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
updateNodeStatus, getEventApiStatus, getRoadmap.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 52/100 · Good | 65/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | ATLASSIAN_HOSTATLASSIAN_EMAILATLASSIAN_TOKENENABLED_TOOLS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 96 | 10 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 21 | 22 |
| Full listing | View Jira MCP | View RoadRaven |
Tools & capabilities
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
RoadRaven tools 22
updateNodeStatusPush a status update to a node. Requires the desktop app to be running and a roadmap loaded. Routes through the agent dispatcher so the change appears in the event-log drawer (Ctrl+Shift+L).getEventApiStatusReturns the current Event API URL, PID, and startedAt — or an error if the app is not running.getRoadmapReturn the full schema tree from the desktop app, with live-event statuses merged in, plus the current `revision` (pass it as expectedRevision on writes to detect stale reads). Pass omitNotes: true for polling (large roadmaps exceed the tool-result limit): it leaves out notes and the createdAt/updatedAt timestamps; fetch notes with getNode/findNodes. Requires the app to be running and a file to be loaded.getNodeReturn a node by UUID, with its immediate parent ID, full ancestor chain (root-to-parent), and the current roadmap `revision`. Status reflects the live overlay if a recent event landed.findNodesSearch nodes by AND-combined filter: titleContains (case-insensitive substring), status, type, metaKey + metaValue, parentId. All fields optional. Returns matching nodes (without their children; use parentId or getNode for those) with their parent IDs.getStatusConfigReturn the loaded roadmap's statusConfig array (display labels/colors for statuses). Agent mutations accept only core node statuses.getTypeConfigReturn the loaded roadmap's typeConfig array (the valid node-type IDs and their visual configuration).getOpenFileReturn filePath (or null if untitled), isUntitled flag, document title, and total nodeCount. Works even when no file is loaded — returns null filePath and isUntitled=false.createNodeAdd a child node under parentId with the given title. Optional: id (UUID or slug — supply it when recovering/recreating a node so its identity stays stable and history/metadata continuity survives file churn; duplicate_id if it already exists), type, core status (defaults to not-started), notes (markdown), metadata. Returns the new node's id. Requires a loaded roadmap.createRoadmapInitialize an in-memory untitled schema (mirrors File > New). Optional: title, statusConfig, typeConfig. The agent must call saveFileAs to persist the new roadmap to disk.renameNodeChange a node's title.updateNodeTypeChange a node's type string. Use getTypeConfig to discover valid types.- +10 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.
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.
RoadRaven
{
"mcpServers": {
"roadraven": {
"command": "npx",
"args": [
"-y",
"@roadraven/mcp@0.9.2"
]
}
}
}
Frequently asked questions
Jira MCP is categorized under Product Management and uses an install path we have not confirmed yet. RoadRaven belongs to Product Management and uses a local stdio subprocess. Pick Jira MCP for product management work and RoadRaven 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.
Jira MCP is listed as free. Auth: api key required. RoadRaven is listed as free. Auth: no auth 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 nguyenvanduocit-jira-mcp and roadraven as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jira MCP has a quality signal of 52/100 (Good) with 4 views, 0 installs and 96 GitHub stars. RoadRaven has 65/100 (Great) with 1 views, 0 installs and 10 GitHub stars.