Skip to main content
Glama

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

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.

Inputs: issueIdOrKey (required), fields, expand, properties, +1 more.

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 2 tools

    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.

    Related MCP Connectors

    Related MCP Servers