Skip to main content
Glama
enesjakozh
CamdenClark

jira-mcp

by CamdenClark
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

JIRA MCP Server

An MCP server that enables Large Language Models (LLMs) to interact with JIRA through standardized tools and context. This server provides capabilities for searching issues using JQL and retrieving detailed issue information.

Features

  • JQL Search: Execute complex JQL queries with pagination support

  • Issue Details: Retrieve detailed information about specific JIRA issues

Related MCP server: JIRA MCP Server

Prerequisites

  • npm installed

  • A JIRA instance with API access

  • JIRA API token or Personal Access Token

  • JIRA user email associated with the API token

Getting JIRA API Credentials

  1. Log in to your Atlassian account at https://id.atlassian.com

  2. Navigate to Security settings

  3. Under API tokens, select "Create API token"

  4. Give your token a meaningful name (e.g., "MCP Server")

  5. Copy the generated token - you won't be able to see it again!

  6. Use this token as your JIRA_API_KEY

  7. Use the email address associated with your Atlassian account as JIRA_USER_EMAIL

Usage

Integration with Claude Desktop

  1. Add the server configuration to Claude Desktop's config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "jira-mcp"],
      "env": {
        "JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
        "JIRA_USER_EMAIL": "your-email@company.com",
        "JIRA_API_KEY": "your-api-token"
      }
    }
  }
}

  1. Restart Claude Desktop to load the new configuration.

Available Tools

1. JQL Search (jql_search)

Executes a JQL search query with customizable parameters.

Parameters:

  • jql (required): JQL query string

  • nextPageToken: Token for pagination

  • maxResults: Maximum number of results to return

  • fields: Array of field names to include

  • expand: Additional information to include

Example:

{
  "jql": "project = 'MyProject' AND status = 'In Progress'",
  "maxResults": 10,
  "fields": ["summary", "status", "assignee"]
}

2. Get Issue (get_issue)

Retrieves detailed information about a specific issue.

Parameters:

  • issueIdOrKey (required): Issue ID or key

  • fields: Array of field names to include

  • expand: Additional information to include

  • properties: Array of properties to include

  • failFast: Whether to fail quickly on errors

Example:

{
  "issueIdOrKey": "PROJ-123",
  "fields": ["summary", "description", "status"],
  "expand": "renderedFields,names"
}

Development

Configuration

Set up your environment variables before running the server. Create a .env file in the root directory:

JIRA_INSTANCE_URL=https://your-instance.atlassian.net
JIRA_USER_EMAIL=your-email@company.com
JIRA_API_KEY=your-api-token

Replace the values with:

  • Your actual JIRA instance URL

  • The email address associated with your JIRA account

  • Your JIRA API token (can be generated in Atlassian Account Settings)

Installation

Installing via Smithery

To install JIRA for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install jira-mcp --client claude

Manual Installation

  1. Clone this repository:

git clone <repository-url>
cd jira-mcp

  1. Install dependencies:

npm install

Running with MCP Inspector

For testing and development, you can use the MCP Inspector:

npm run inspect

Adding New Tools

To add new tools, modify the ListToolsRequestSchema handler in index.js:

server.setRequestHandler(ListToolsRequestSchema, async () => {
  return {
    tools: [
      // Existing tools...
      {
        name: "your_new_tool",
        description: "Description of your new tool",
        inputSchema: {
          // Define input schema...
        }
      }
    ]
  };
});

Then implement the tool in the CallToolRequestSchema handler.

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a PR.

Available Tools

2 tools
get_issueC

Retrieve details about an issue by its ID or key.

ParametersJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesID or key of the issue
fieldsNoFields to include in the response
expandNoAdditional information to include in the response
propertiesNoProperties to include in the response
failFastNoFail quickly on errors

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details, implying a read-only operation, but doesn't mention error handling (e.g., what happens if the ID/key is invalid), rate limits, authentication needs, or response format. This leaves significant gaps for an agent to understand how to use it effectively.

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

Conciseness5/5

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

The description is a single, clear sentence that efficiently conveys the core purpose without any unnecessary words. It's front-loaded and easy to parse, making it highly concise and well-structured for quick understanding.

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

Completeness2/5

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

Given the complexity of 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what details are retrieved, how to handle optional parameters like 'fields' or 'expand', or what the response looks like. For a tool with multiple parameters and no structured output information, more context is needed to guide proper usage.

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

Parameters3/5

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

The input schema has 100% description coverage, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond implying retrieval by 'ID or key', which aligns with the 'issueIdOrKey' parameter but doesn't elaborate on usage. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Retrieve') and resource ('details about an issue'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from the sibling tool 'jql_search', which likely serves a different purpose (searching vs. retrieving by ID/key).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'jql_search'. It mentions retrieving by 'ID or key', which implies a specific use case, but doesn't clarify when to choose this over a search tool or address any prerequisites or exclusions.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: get_issue retrieves a single issue by ID/key, while jql_search performs broader queries using JQL. There is no overlap or ambiguity between them, as they serve different use cases (specific lookup vs. flexible search).

Naming Consistency5/5

Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: get_issue and jql_search. The naming is predictable and readable, with no deviations or mixed conventions.

Tool Count2/5

With only 2 tools, this server feels severely under-scoped for a Jira integration. A typical Jira MCP would need more operations like create_issue, update_issue, or list_projects to cover basic workflows. The current set is too thin for meaningful agent interaction.

Completeness2/5

The tool surface is significantly incomplete for Jira's domain. While get_issue and jql_search provide read/search capabilities, there are major gaps in CRUD operations (no create, update, or delete) and missing lifecycle management (e.g., transitions, comments). This will cause agent failures in common scenarios.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CamdenClark/jira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server