MCP.so
Sign In

Jira MCP Server

@uddeshya-23

Basic information

Category

Version Control

Transports

stdio

Author

uddeshya-23

About Jira MCP Server

Mcp server in typescript to connect with Jira Analyze the issues

Jira MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Jira MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Jira MCP Server?

The Jira MCP Server is a Model Context Protocol implementation that enables AI models to interact with Jira through a standardized interface, integrating with the full Jira REST API.

How to use Jira MCP Server?

Install via npm install @modelcontextprotocol/server-jira, configure required environment variables (JIRA_HOST, JIRA_API_TOKEN, JIRA_EMAIL) and optional ones (PORT, POOL_SIZE), then start the server with npm run dev (development) or npm start (production). The server exposes HTTP endpoints for fetching issue details, current sprint details, and workload analytics.

Key features of Jira MCP Server

  • Full Jira REST API integration
  • Connection pooling for optimal performance
  • Comprehensive error handling
  • Type-safe implementation
  • Built-in rate limiting
  • Request logging and monitoring

Use cases of Jira MCP Server

  • Retrieve Jira issue details by key
  • Fetch current sprint information
  • Obtain workload analytics for teams
  • Enable AI assistants to query and interact with Jira data

Frequently asked questions

1

What are the runtime dependencies for Jira MCP Server?

Node.js 14 or higher and npm 6 or higher are required.

2

How do I configure the server to connect to my Jira instance?

Set the environment variables `JIRA_HOST` (your domain), `JIRA_API_TOKEN` (API token), and `JIRA_EMAIL` (email) before starting the server.

3

What endpoints does the server expose?

The server provides `GET /health` for health checks, `GET /api/v1/issues/:issueKey` for issue details, `GET /api/v1/sprint/current` for current sprint, and `GET /api/v1/analytics/workload` for workload analytics.

4

Does the server have any rate limiting or monitoring?

Yes, built-in rate limiting and request logging are included as core features.

5

Where does the data live?

Data is stored in Jira Cloud; the server interacts with Jira via its REST API and does not store any data locally.

Comments

More Version Control MCP servers