Jira MCP
Jira & Confluence MCP: 24 tools for issues, sprints, comments, transitions & wiki.
Connector by raalarcon9705 · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/raalarcon9705-jira-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 11 read · 10 write · 3 delete
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- Not scanned yet
- Runs as
- Node.js package
Tools by what they do 24
Read from the source code; the running server may list different tools.
Read 11 · Look things up without changing anything.
get_agile_boardsget_commentsget_current_userget_issueget_issue_typesget_projectsget_sprint_issuesget_sprintsget_transitionsget_usersquery_wiki
Write 10 · Create, change, send or run things.
assign_issueclose_sprintcreate_commentcreate_issuecreate_sprintmove_issue_to_sprinttransition_issueupdate_commentupdate_issueupdate_sprint
Delete 3 · Delete, drop, revoke or wipe things.
delete_commentdelete_issuedelete_sprint
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
JIRA_API_TOKEN
Other settings (environment variables or headers).
JIRA_EMAILJIRA_HOST
Tools (24)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
assign_issueAssign a Jira issue to a user
close_sprintClose and complete a sprint. This action requires the sprint to be in the "active" state. Once closed, the sprint cannot be reopened.
create_commentAdd a comment to a Jira issue. Supports plain text or Markdown for rich formatting (headings, lists, code blocks, links, etc.). Markdown is automatically converted to ADF. For mentions, use format: @[accountId:displayName] (get accountId from get_users tool). Returns comment ID and creation details.
create_issueCreate a new Jira issue (Bug, Story, Task, Epic, etc.) or subtask. Returns the created issue key, ID, and URL. Use get_issue_types to find valid issueType values for the project. To create a subtask, specify the parent issue key.
create_sprintCreate a new sprint. Sprint name and origin board ID are required. Start date, end date, and goal are optional.
delete_commentDelete a comment from a Jira issue
delete_issuePermanently delete a Jira issue. This action cannot be undone. Use with caution. Returns success confirmation.
delete_sprintDelete a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible.
get_agile_boardsGet all agile boards available in the Jira instance. Required to find board IDs for sprint operations.
get_commentsGet comments for a Jira issue with pagination support. Returns comments with pagination metadata to help navigate through large comment lists.
get_current_userGet information about the current authenticated user
get_issueRetrieve detailed information about a specific Jira issue including status, assignee, description, comments, and workflow data. Use this to get current state before making updates.
get_issue_typesGet all available issue types (Bug, Story, Task, Epic, etc.) for a specific project. Returns type names, IDs, descriptions, and workflow information. Required before creating issues to know valid issueType values.
get_projectsRetrieve all Jira projects accessible to the authenticated user. Returns project keys, names, IDs, and basic metadata. Use this to discover available projects before creating issues or performing other operations.
get_sprint_issuesGet all issues in a specific sprint. Useful for viewing what tickets are currently in a sprint.
Show 9 more tools
get_sprintsGet all sprints for a specific board. Returns sprint information including ID, name, state, and dates.
get_transitionsGet available transitions for a Jira issue
get_usersSearch for users in Jira
move_issue_to_sprintMove an issue to a specific sprint. This is the main function to add tickets to the current sprint.
query_wikiGet Confluence page content by specific code (like F4CjNw).
transition_issueMove a Jira issue to a different status/state
update_commentUpdate an existing comment on a Jira issue. Supports plain text or Markdown for rich formatting (headings, lists, code blocks, links, etc.). Markdown is automatically converted to ADF. For mentions, use format: @[accountId:displayName] (get accountId from get_users tool).
update_issueUpdate fields of an existing Jira issue or convert to subtask. Only provided fields will be updated. Use get_issue first to see current values. Returns success confirmation.
update_sprintUpdate sprint information (name, dates, goal, state). Only provided fields will be updated. For closed sprints, only name and goal can be updated.
Signals
- Stars
- 6
- Forks
- 0
- Open issues
- 1
- Last commit
- May 29, 2026 (5 months ago)
- Last release
- Apr 22, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.raalarcon9705/jira-mcp- Version
- 1.0.82
- Auth
- API key
- Packages
- npm raalarcon-jira-mcp-server
- License
- MIT
- Repository
- github.com/raalarcon9705/jira-mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Cite this page
Jira MCP. Agent Mart. https://agentmart.dev/connectors/raalarcon9705-jira-mcp (last updated 2026-10-24)