home / mcp / jira mcp server

Jira MCP Server

Exposes Jira functionality via MCP with OpenAPI integration, secure authentication, and multiple transports.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "brukhabtu-jira-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "JIRA_BASE_URL=https://yourcompany.atlassian.net",
        "-e",
        "[email protected]",
        "-e",
        "JIRA_API_TOKEN=your-api-token",
        "ghcr.io/brukhabtu/jira-mcp:latest"
      ],
      "env": {
        "MCP_PORT": "8000",
        "JIRA_TIMEOUT": "30",
        "JIRA_API_USER": "[email protected]",
        "JIRA_BASE_URL": "https://yourcompany.atlassian.net",
        "MCP_LOG_LEVEL": "INFO",
        "MCP_TRANSPORT": "stdio",
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_OPENAPI_SPEC_PATH": "bundled",
        "MCP_ENABLE_SECURITY_FILTERING": "true"
      }
    }
  }
}

You deploy a Jira MCP Server to expose Jira data and actions through the Model Context Protocol, letting MCP clients safely read Jira information such as issues, projects, boards, and dashboards via a portable, type-safe interface.

How to use

You run the Jira MCP Server in a client-friendly way and connect with an MCP client to access Jira data. The server fetches Jira’s OpenAPI specification, generates MCP tools for Jira endpoints, and enforces security filtering by default to allow read-only operations. Use a compatible MCP client to query issues, projects, users, boards, sprints, dashboards, and filters through the MCP interface.

How to install

Prerequisites you need on your machine:

Docker is used to run the Jira MCP Server container.

Prepare your Jira API access by creating an API token and noting your Jira instance URL.

Step 1: Run the Jira MCP Server with Docker.

docker run --rm -i \
  -e JIRA_BASE_URL=https://yourcompany.atlassian.net \
  -e [email protected] \
  -e JIRA_API_TOKEN=your-api-token \
  ghcr.io/brukhabtu/jira-mcp:latest

Configuration and security notes

Environment variables shown in the run command are the key configuration inputs for the Jira MCP Server when using Docker. You can customize them to point to your Jira instance and credentials.

Optional security and transport settings can be controlled via MCP-related environment options when you integrate with your MCP client setup.

Security and troubleshooting

Security filtering is enabled by default to block destructive operations and only expose safe read-only endpoints. If you need to adjust this behavior, review the security configuration options in your MCP environment to enable or disable filtering carefully.

If you encounter authentication or connection issues, verify that your Jira API token is correct and that the Jira base URL matches your Jira instance. Ensure the container has network access to the Jira instance.

Available tools

read_issues

Read and search Jira issues, allowing clients to query issue data and perform safe reads.

get_project_info

Retrieve metadata about Jira projects including descriptions, statuses, and metadata.

get_user_data

Fetch information about Jira users and teams, enabling lookup of user details and group memberships.

get_agile_data

Access agile boards, sprints, and related planning data to surface sprint information and board configurations.

get_dashboards

Expose dashboards and saved filters for querying and display in MCP clients.

get_system_info

Expose system-level information and field metadata useful for client applications.