Skip to main content
Glama
trongtai1801

jira-mcp

by trongtai1801
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jira-mcp

MCP server for fetching Jira issue data.

Required Settings

Python

This project requires Python 3.14 or newer.

The required version is declared in:

  • .python-version

  • pyproject.toml

  • uv.lock

Dependency Management

Use uv as the Python dependency and virtual environment manager for this project.

Install uv if it is not already available:

curl -LsSf https://astral.sh/uv/install.sh | sh

Then install the project dependencies from pyproject.toml and uv.lock:

uv sync

Do not install dependencies directly with pip; keep dependency changes in pyproject.toml and refresh the lockfile with uv.

Environment Variables

Create a local .env file from the example file:

cp .env.example .env

Set these values in .env:

JIRA_EMAIL=your-email@example.com
JIRA_API_TOKEN=your-jira-token
JIRA_DOMAIN=your-company.atlassian.net

Required by the current code:

  • JIRA_EMAIL: Email address used for Jira API authentication.

  • JIRA_API_TOKEN: Jira API token for the account above.

  • JIRA_DOMAIN: Jira site domain, for example your-company.atlassian.net.

Included in .env.example but not currently used by main.py:

  • MODEL_NAME

  • OPENAI_API_KEY

Jira Access

The Jira API call uses:

https://<JIRA_DOMAIN>/rest/api/3/issue/<ISSUE_KEY>

The Jira account must have permission to view the requested issue. For Atlassian Cloud, use an API token rather than your account password.

Related MCP server: Work Integrations MCP

Running

Run the MCP server over stdio:

uv run main.py

The server exposes the fetch_jira MCP tool.

Cursor MCP Setup

To use this MCP server from another project in Cursor, create or update this file in that project:

.cursor/mcp.json

Add the Jira MCP server configuration:

{
  "mcpServers": {
    "jira-server": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/jira-mcp",
        "run",
        "main.py"
      ]
    }
  }
}

Replace /path/to/jira-mcp with the local path to this project on your computer.

Available Tools

1 tool
fetch_jiraD
ParametersJSON Schema
NameRequiredDescriptionDefault
issue_keyYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev0.1.0
    • First observedfetch_jira
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion with other tools. The tool's purpose is unambiguous within the set, even without a description.

Naming Consistency5/5

The single tool name 'fetch_jira' follows a clear verb_noun pattern, consistent with common naming conventions. There are no other tools to cause inconsistency.

Tool Count2/5

A single tool for a Jira server is far too few to cover typical operations like creating, updating, or deleting issues. It falls in the 'too few' category, making the server feel incomplete for its apparent purpose.

Completeness1/5

The server only provides a 'fetch' operation, lacking any create, update, delete, or search capabilities. This severely limits its usefulness for Jira workflows, leaving huge gaps in functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Jira Server

    edrich13
    A
    license
    A
    quality
    C
    maintenance
    An MCP server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It enables users to perform CRUD operations on issues, search with JQL, manage comments, and list projects through the Jira REST API.
    12
    342 npm
    13
    MIT

  • Work Integrations MCP

    NazarKY
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.
    408 npm
    MIT