Skip to main content
Glama
jira-mcp-server

jira-mcp-server

by thisIsRasel

jira-mcp-server

Stdio-based MCP server exposing Jira tools (search, get/create issue, comment, assign, transition, list projects).

Image: thisisrasel/jira-mcp-server (tags: latest, 1.0.0)

Environment variables

Var

Required

Notes

JIRA_BASE_URL

yes

e.g. https://your-jira-instance.com

JIRA_TOKEN

no

Bearer auth; if set, takes priority over username/password

JIRA_USERNAME

only if no JIRA_TOKEN

basic auth

JIRA_PASSWORD

only if no JIRA_TOKEN

basic auth

See .env.example.

Related MCP server: jira-cli-mcp

Run via MCP client

Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json), passing credentials as env vars on the docker run command rather than baking them into the image:

{
  "mcpServers": {
    "jira": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "JIRA_BASE_URL",
        "-e", "JIRA_TOKEN",
        "thisisrasel/jira-mcp-server:latest"
      ],
      "env": {
        "JIRA_BASE_URL": "https://your-jira-instance.com",
        "JIRA_TOKEN": "your-token"
      }
    }
  }
}

For basic auth instead of a token, swap the -e/env entries for JIRA_USERNAME and JIRA_PASSWORD.

Build & push

docker build -t thisisrasel/jira-mcp-server:1.0.0 -t thisisrasel/jira-mcp-server:latest .
docker push thisisrasel/jira-mcp-server:1.0.0
docker push thisisrasel/jira-mcp-server:latest

Available Tools

7 tools
jira_add_commentAdd Jira CommentC

Add comment to issue

Inputs: comment (required), issueKey (required).

jira_assign_issueAssign Jira IssueC

Assign issue to user

Inputs: issueKey (required), username (required).

jira_create_issueCreate Jira IssueC

Create a Jira task

Inputs: summary (required), projectKey (required), description (required), issueType.

jira_get_issueGet Jira IssueC

Retrieve Jira issue details

Inputs: issueKey (required).

jira_projectsList Jira ProjectsC

Get Jira projects

Inputs: no named parameters.

jira_transition_issueTransition Jira IssueC

Move issue to another workflow state

Inputs: issueKey (required), transitionId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct Jira operation: search, retrieve, create, comment, assign, transition, and list projects. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the 'jira_' prefix and use snake_case, with most following a verb_noun pattern (e.g., jira_get_issue). The exception is jira_projects, which is a simple noun rather than 'list_projects', but this is a minor deviation.

    Tool Count5/5

    With 7 tools, the server is well-scoped for common Jira operations. Each tool covers a core feature without unnecessary bloat or missing essentials.

    Completeness3/5

    The set covers create, read, search, comment, assign, and transition, but lacks an update operation (e.g., jira_update_issue), which is a core part of issue lifecycle management. This is a notable gap that agents may need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Jira integration with stdio transport. Enables reading, writing, and managing Jira issues and projects directly from Claude Desktop. Supports issue creation, updates, comments, JQL search, and project management.
      23
      2,102 npm
      14
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Small MCP server for connecting to enterprise Jira using a personal access token. It enables issue operations, project listing, JQL searches, and attachment handling.
      17
      MIT