Get the FREE Ultimate OpenClaw Setup Guide →

jira

A test of jira mcp server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio ks-gen-ai-jira-mcp-server node /PATH_TO_THE_PROJECT/build/index.js \
  --env JIRA_URL="https://XXXXXXXX.atlassian.net" \
  --env JIRA_API_KEY="KEY_FROM : https://id.atlassian.com/manage-profile/security/api-tokens" \
  --env JIRA_API_MAIL="Your email"

How to use

This MCP server exposes a set of Jira-related tools that let you query, create, modify, and manage Jira data through the MCP interface. You can run JQL queries, fetch ticket summaries, create and edit tickets, list projects and statuses, delete or reassign tickets, and attach files from public URLs or Confluence pages. Each tool accepts structured parameters (for example, project keys, issue IDs, summaries, descriptions, and labels) and returns Jira objects or operation results that you can feed into subsequent prompts. The server is designed to demonstrate core MCP concepts by providing concrete Jira operations that can be composed into multi-step workflows.

How to install

Prerequisites:

  • Node.js and npm installed on your system
  • Access to the project repository and build artifacts (build/index.js)
  1. Install dependencies
npm install
  1. Build the server (TypeScript project)
npm run build
  1. Run the server locally for development
npm run watch
  1. For Claude Desktop or external integration, configure the MCP server in your client config (example shown in the Installation section of the README):
{
  "mcpServers": {
    "Jira communication server": {
      "command": "node",
      "args": ["/PATH_TO_THE_PROJECT/build/index.js"],
      "env": {
        "JIRA_URL": "https://XXXXXXXX.atlassian.net",
        "JIRA_API_MAIL": "Your email",
        "JIRA_API_KEY": "KEY_FROM : https://id.atlassian.com/manage-profile/security/api-tokens"
      }
    }
  }
}

Additional notes

Tips:

  • Ensure your JIRA_URL, JIRA_API_MAIL, and JIRA_API_KEY are kept secure and not checked into source control.
  • The server uses stdio for MCP communication; if you need debugging, run with npm run inspector as described in the README to access the MCP Inspector tools.
  • When using attach operations, ensure the target Jira project and issue IDs exist and that the API key has the necessary permissions.
  • If you encounter authentication failures, verify that API tokens are active and not expired.
  • For local development, use the watch mode to auto-rebuild on code changes.

Related MCP Servers

Sponsor this space

Reach thousands of developers