MCP.so
Sign In

Jira MCP Server

@MaximilianoGarciaRoe

Basic information

Category

Version Control

Transports

stdio

Author

MaximilianoGarciaRoe

About Jira MCP Server

No overview available yet

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?

An MCP server that enables interaction with Jira’s API, allowing users to retrieve issue information. It is intended for developers using Codeium’s MCP framework.

How to use Jira MCP Server?

Install dependencies with npm, then configure the server in your Codeium MCP config file (~/.codeium/windsurf/mcp_config.json) by specifying the command npx -y tsx /path/to/jira_mcp/main.ts and setting the environment variables JIRA_USERNAME, JIRA_API_KEY, and JIRA_BASE_URL. The server is started automatically by Codeium when needed. Available commands include get_issue.

Key features of Jira MCP Server

  • Retrieve details of a Jira issue by its key (e.g., "RMPRE-123")
  • Works with any Jira instance accessible via API
  • Integrates with Codeium’s MCP workflow
  • Requires only Node.js v16 or higher

Use cases of Jira MCP Server

  • Fetching issue details during AI‑assisted development in Codeium
  • Automating issue lookups without leaving the editor

Frequently asked questions

1

What prerequisites are needed to run the server?

Node.js v16 or higher, npm or yarn, and a Jira account with API access.

2

How do I configure authentication?

Provide a valid Jira username, API key, and base URL as environment variables (`JIRA_USERNAME`, `JIRA_API_KEY`, `JIRA_BASE_URL`) in the MCP config file.

3

What transport does the server use?

The server is started via command line using `npx` and `tsx`; details of the transport protocol are not specified in the README.

4

Are there any known limitations?

The README only documents one command (`get_issue`); no other capabilities or limits are mentioned.

Comments

More Version Control MCP servers