Skip to content
Agentmart
Submit a tool

MCP Jira Stdio

MCP server for Jira Cloud — issues, search, comments, attachments, transitions.

Connector by freema · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 14
Write a review

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/freema-mcp-jira-stdio

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.

We use your email only for this newsletter. Privacy

About

MCP server for Jira Cloud — issues, search, comments, attachments, transitions.

No 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, install config and code. Checked Oct 25, 2026.

Tools
15 read · 7 write · 1 delete
Secrets
1 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Node.js package

Tools by what they do 23

Read from the source code; the running server may list different tools.

Read 15 · Look things up without changing anything.

  • jira_get_attachments
  • jira_get_comments
  • jira_get_create_meta
  • jira_get_custom_fields
  • jira_get_issue
  • jira_get_issue_graph
  • jira_get_issue_types
  • jira_get_my_issues
  • jira_get_priorities
  • jira_get_project_info
  • jira_get_statuses
  • jira_get_transitions
Show 3 more tools
  • jira_get_users
  • jira_get_visible_projects
  • jira_search_issues

Write 7 · Create, change, send or run things.

  • jira_add_attachment
  • jira_add_comment
  • jira_create_issue
  • jira_create_issue_link
  • jira_create_subtask
  • jira_transition_issue
  • jira_update_issue

Delete 1 · Delete, drop, revoke or wipe things.

  • jira_delete_attachment

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_BASE_URL
  • JIRA_EMAIL
  • LOG_LEVEL
  • MCP_REDACT_SENSITIVE

Network hosts it talks to 6

  • company.atlassian.net · found in code
  • github.com · found in code
  • glama.ai · found in code
  • tomasgrasl.cz · found in code
  • your-instance.atlassian.net · found in code
  • your.atlassian.net · found in code

Files it touches

  • Your home directory (~)
  • Any path the agent passes to its tools

Tools (23)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • jira_add_attachment

    Uploads an attachment (image, document, etc.) to a Jira issue. **EFFICIENT METHOD (recommended for large files):** - fileUrl: Provide URL to remote file - MINIMAL tokens (~60 tokens) Example: Upload to Dropbox/S3/imgur first, then provide URL **DIRECT METHOD (for small files):** - content: Base64 encoded content - WARNING: HIGH token cost (~330,000 tokens for 1MB file) Only suitable for small files (< 500 KB) Returns attachment metadata including ID and download URL. To reference the image in a comment or description, use wiki markup: !filename.png! or !filename.png|thumbnail!

  • jira_add_comment

    Adds a comment to an issue. Supports visibility restrictions for groups or roles. Comment format is controlled by the "format" parameter (default: markdown). Returns the created comment with author details and timestamp.

  • jira_create_issue

    Creates a new Jira issue in the specified project. Supports setting issue type, priority, assignee, labels, components, and custom fields. Description format is controlled by the "format" parameter (default: markdown). For required custom fields, supply them via customFields (e.g., { "customfield_12345": { id: "..." } }). Returns the created issue with all details.

  • jira_create_issue_link

    Creates a link between two Jira issues. Supports common link types like "blocks", "relates", "duplicates", and "clones". Use this to establish relationships between issues.

  • jira_create_subtask

    Creates a subtask under an existing parent issue. Automatically determines the correct project and subtask issue type. Supports setting priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown).

  • jira_delete_attachmentcan change or delete data

    Deletes an attachment from Jira by its attachment ID. Use jira_get_attachments to find attachment IDs.

  • jira_get_attachmentsread-only

    Lists all attachments on a Jira issue. Returns attachment metadata including filename, size, MIME type, author, and download URL.

  • jira_get_commentsread-only

    Retrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Supports pagination for issues with many comments.

  • jira_get_create_metaread-only

    Retrieves 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_fieldsread-only

    Retrieves 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_issueread-only

    Retrieve 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_get_issue_graphread-only

    Build a dependency/relationship graph starting from a seed issue. Returns a map of connected issues (parent/child hierarchy, blocks, relates to, duplicates, etc.) with nodes and edges, plus a Mermaid diagram for visualization. Use this to understand how issues are connected across epics, stories, and subtasks.

  • jira_get_issue_typesread-only

    Retrieves 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_my_issuesread-only

    Retrieves 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_prioritiesread-only

    Retrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions.

Show 8 more tools
  • jira_get_project_inforead-only

    Retrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list.

  • jira_get_statusesread-only

    Retrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information.

  • jira_get_transitionsread-only

    Retrieves all available workflow transitions for a Jira issue. Use this to discover which status changes are possible for an issue before calling jira_transition_issue.

  • jira_get_usersread-only

    Search for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination.

  • jira_get_visible_projectsread-only

    Retrieves all projects accessible to the authenticated user. Returns project keys, names, descriptions, and basic metadata.

  • jira_search_issuesread-only

    Search 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_transition_issue

    Transitions a Jira issue to a new workflow status (e.g., "To Do" -> "In Progress" -> "Done"). Use jira_get_transitions first to discover available transitions. Supports adding a comment and setting resolution during the transition.

  • jira_update_issue

    Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, components, and fix versions. Description format is controlled by the "format" parameter (default: markdown). Only specified fields will be updated.

Signals

Stars
14
Forks
9
Open issues
0
Last commit
Oct 2, 2026 (26 days ago)
Last release
Oct 2, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.freema/mcp-jira-stdio
Version
1.12.1
Auth
API key
Packages
npm mcp-jira-stdio
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from freema

Cite this page

MCP Jira Stdio. Agent Mart. https://agentmart.dev/connectors/freema-mcp-jira-stdio (last updated 2026-10-24)