Skip to main content
Glama
avidianity

@avidian/mcp-jira

by avidianity

@avidian/mcp-jira

MCP server for Jira Cloud — gives AI agents full context and control over Jira issues, projects, sprints, and workflows.

Installation

npm (requires Node.js ≥ 20)

npm install -g @avidian/mcp-jira

Compiled binary (no runtime needed)

sh -c "$(curl -fsSL https://raw.githubusercontent.com/avidianity/mcp-jira/main/install.sh)"

Or download manually from GitHub Releases.

Related MCP server: Jira Cloud MCP Server

Configuration

Set these environment variables:

Variable

Description

JIRA_BASE_URL

Your Jira Cloud URL (e.g., https://your-domain.atlassian.net)

JIRA_USER_EMAIL

Email of the Jira user

JIRA_API_TOKEN

API token (generate here)

Usage

stdio (default — Claude Desktop, VS Code, Cursor)

mcp-jira

HTTP (Streamable HTTP transport)

mcp-jira --transport http --port 5485

MCP client configuration

{
  "mcpServers": {
    "jira": {
      "command": "mcp-jira",
      "env": {
        "JIRA_BASE_URL": "https://your-domain.atlassian.net",
        "JIRA_USER_EMAIL": "you@example.com",
        "JIRA_API_TOKEN": "your-api-token"
      }
    }
  }
}

Data formats (agent boundary)

Direction

Format

Notes

Agent → MCP (rich text)

Markdown

Descriptions, comments, worklog comments. Converted to Jira ADF before REST calls.

MCP → Agent (rich text)

Markdown

ADF from Jira is converted back to Markdown. Never raw ADF.

MCP → Agent (structured data)

TOON

Lists, issue details, search hits, metadata, etc. Token-efficient vs JSON.

MCP → Agent (simple ack)

Plain text

Short success/error lines (Created issue: PROJ-1).

MCP → Agent (media)

Image / resource / path

Unchanged binary/path modes for attachments.

Mentions in Markdown: @[accountId] or @[Display Name|accountId] (plain @Name is not a mention).

Why Markdown ships below the TOON, not inside it

TOON has no multi-line scalar. A value containing line breaks is encoded as one quoted physical line with \n escapes, so a long comment or description becomes a single multi-thousand-character line - and clients that cap line length when rendering tool output silently drop its tail.

Tools that return prose therefore split the response: structured fields stay in the TOON envelope, and each Markdown body follows below it under a banner, with real line breaks.

startAt: 0
end: 2
total: 12
nextStartAt: 2

--- comment 742603 (Cyril Reyes, 2025-08-10T14:22:11.000+0000) ---
FROM STAGING:

- first finding
- second finding

--- comment 742100 (Mekky, 2025-08-09T09:00:00.000+0000, edited 2025-08-09T11:04:00.000+0000) ---
Short reply.

get_issue uses --- description ---, and get_worklogs uses --- worklog <id> comment ---.

Tools

Issues

Tool

Description

get_issue

Full issue details (TOON fields + Markdown description block)

search_issues

Search via JQL with pagination

create_issue

Create issue; supports components, fixVersions, custom fields

update_issue

Update issue fields (same field support as create)

delete_issue

Delete an issue (optionally its subtasks)

get_issue_transitions

Get available status transitions

transition_issue

Change issue status

get_issue_changelog

Get the field-by-field change history

Comments

Tool

Description

get_issue_comments

List comments as Markdown blocks; optional sort and fuzzy search

add_comment

Add a comment (Markdown, supports @[id] mentions)

update_comment

Edit an existing comment

delete_comment

Delete a comment

Worklogs

Tool

Description

get_worklogs

List logged work on an issue

add_worklog

Log time (e.g. 3h, 30m, 1d 2h)

update_worklog

Edit a work log entry

delete_worklog

Delete a work log entry

Participation

Tool

Description

list_watchers

List watchers on an issue

add_watcher

Add a watcher (self or by account)

remove_watcher

Remove a watcher

get_votes

Get vote count and voters

add_vote

Vote for an issue

remove_vote

Remove your vote

Tool

Description

link_issues

Link two issues together

get_link_types

List available issue link types

delete_issue_link

Delete a link by ID

add_remote_link

Attach an external URL to an issue

list_attachments

List all attachments on an issue (shows image/media file IDs)

get_image

Fetch an image (output: base64 or path)

get_video

Fetch a video (output: base64 or path)

get_text_file

Fetch a text/source file: output text (inline) or path (raw, faithful)

get_binary_file

Fetch a binary file (output: base64 or path)

add_attachment

Upload a file (text or base64 binary)

delete_attachment

Delete an attachment by ID

Boards & sprints

Tool

Description

list_boards

List boards (optionally by project)

get_board

Get board configuration and columns

get_sprint

Get active/future/closed sprints for a board

create_sprint

Create a sprint

start_sprint

Start (activate) a sprint

complete_sprint

Complete (close) a sprint

move_issues_to_sprint

Move issues into a sprint

move_issues_to_backlog

Move issues to the backlog

add_issues_to_epic

Add issues to an epic (none to unlink)

Projects

Tool

Description

list_projects

List accessible projects

get_project

Get project details, issue types, components

list_versions

List project versions/releases

create_version

Create a version

update_version

Update a version (e.g. mark released)

list_components

List project components

create_component

Create a component

Users & metadata

Tool

Description

get_user

Search users by name or email

get_current_user

Get the authenticated user

list_assignable_users

List users assignable to a project/issue

assign_issue

Assign or unassign an issue

list_issue_types

List issue types

list_statuses

List workflow statuses

list_priorities

List priorities

list_fields

List fields incl. custom field IDs

get_create_meta

Required/available fields for create

list_labels

List labels

Mentions

add_comment and update_comment accept Jira user mentions in the Markdown body:

  • @[accountId] — mention by account ID

  • @[Display Name|accountId] — mention with a friendly label

Use get_user or list_assignable_users to look up account IDs.

Development

# Install dependencies
bun install

# Run in dev mode
bun run dev

# Type check
bun run typecheck

# Lint
bun run lint

# Format
bun run format

# Build for npm
bun run build

# Compile native binary
bun run compile

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.
    112 npm
    4
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A comprehensive, production-ready MCP server for seamless Jira Cloud integration, enabling AI agents and custom applications to manage boards, issues, users, projects, and workflows via natural language commands.
    642 npm
    4
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that provides AI assistants with access to Jira Cloud for issue management, search, and workflow operations.
    -