MCP Server for Jira

@rihofujino

Repository

About MCP Server for Jira

No overview available yet

#jira #mcp-server #project-management

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

Tools

No tools detected

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

Overview

What is MCP Server for Jira?

MCP Server for Jira is an MCP server that connects to the Jira API. It allows you to search, create, update, and manage Jira issues and comments programmatically.

How to use MCP Server for Jira?

Install dependencies with npm install, copy .env.example to .env, and fill in your Jira API URL, email, and token. Start the server with npm run dev (development) or npm start (production). The server exposes REST endpoints under /api/jira/.

Key features of MCP Server for Jira

Search Jira issues using JQL queries
Get detailed information for a single issue
Create new Jira issues with custom fields
Update existing issue fields
Add comments to issues
Transition issue statuses (workflow steps)

Use cases of MCP Server for Jira

Automate issue creation from external tools
Fetch issue details for reporting or dashboards
Update issue statuses as part of CI/CD pipelines
Add context comments to issues automatically

FAQ from MCP Server for Jira

What environment variables are required?

JIRA_API_URL (e.g. https://your-domain.atlassian.net/rest/api/3), JIRA_API_EMAIL, and JIRA_API_TOKEN must be set. Optional variables include PORT (default 3000) and LOG_LEVEL.

How do I search for issues?

Send a GET request to /api/jira/issues with the required jql query parameter (e.g., project=PROJ). Optionally set maxResults (default 50).

How do I create a new issue?

Send a POST request to /api/jira/issues with a JSON body containing the fields object, including project.key, summary, and issuetype.id. Priority and other fields are optional.

How do I change an issue’s status?

Send a POST request to /api/jira/issues/:issueKey/transitions with the transitionId in the body.

Where are logs stored?

Logs are saved to logs/combined.log (all logs) and logs/error.log (errors only). Log level is controlled by the LOG_LEVEL environment variable.

Frequently asked questions

What environment variables are required?

`JIRA_API_URL` (e.g. `https://your-domain.atlassian.net/rest/api/3`), `JIRA_API_EMAIL`, and `JIRA_API_TOKEN` must be set. Optional variables include `PORT` (default 3000) and `LOG_LEVEL`.

How do I search for issues?

Send a GET request to `/api/jira/issues` with the required `jql` query parameter (e.g., `project=PROJ`). Optionally set `maxResults` (default 50).

How do I create a new issue?

Send a POST request to `/api/jira/issues` with a JSON body containing the `fields` object, including `project.key`, `summary`, and `issuetype.id`. Priority and other fields are optional.

How do I change an issue’s status?

Send a POST request to `/api/jira/issues/:issueKey/transitions` with the `transitionId` in the body.

Where are logs stored?

Logs are saved to `logs/combined.log` (all logs) and `logs/error.log` (errors only). Log level is controlled by the `LOG_LEVEL` environment variable.

Comments

Basic information

More Version Control MCP servers

Atlassian Bitbucket MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get, comment, search). Connects AI directly to version control workflows through the standard MCP interface.

157