JIRA MCP Server š
@karolswdev
å ³äŗ JIRA MCP Server š
ęę ę¦č§
åŗę¬äæ”ęÆ
é ē½®
ęę ę åé ē½®
评ęå”åØē README äøę²”ęåÆč§£ęē MCP é ē½®åļ¼čÆ·åå¾ä»£ē ä»åŗę„ēå®č£ 诓ęć
代ē ä»åŗå·„å ·
ęŖę£ęµå°å·„å ·
å·„å
·ęÆä» README äøčŖåØęåēć结ę¤č
åÆä»„åØ ## Tools ę é¢äøååŗå·„å
·,å³åÆå”«å
čæéØåå
容ć
ę¦č§
What is JIRA MCP Server?
A flexible Go server that implements the Model Context Protocol (MCP) to interact with the JIRA Cloud REST API. It bridges AI assistants or developer tools (MCP clients) with JIRA, enabling automated issue management, searching, and Epic tracking through a standardized interface.
How to use JIRA MCP Server?
Clone the repository, set required environment variables (JIRA_MCP_JIRA_URL, JIRA_MCP_JIRA_USER_EMAIL, JIRA_MCP_JIRA_API_TOKEN), and run the server using make run (Go) or Docker (build image then make docker-run). The server listens on the configured port (default 8080) and exposes MCP-compatible endpoints.
Key features of JIRA MCP Server
- Exposes JIRA actions via standard MCP endpoints
- Create issues, search with JQL, retrieve details, and fetch Epic issues
- Flexible configuration via environment variables, config file, or defaults
- Ready for containerized deployment with Docker and Docker Compose
- Comprehensive unit and integration tests
- Clean architecture with dependency injection and structured logging
Use cases of JIRA MCP Server
- Automate issue creation from AI assistant conversations
- Query and display JIRA project status in development tools
- Fetch all issues in an Epic for sprint planning via LLMs
- Integrate task management into custom MCP-powered workflows
- Search and retrieve issue details without leaving the coding environment
FAQ from JIRA MCP Server
What are the prerequisites?
You need Go 1.20+ (for local build), a JIRA Cloud instance, and a JIRA API token associated with a user email. Docker and Docker Compose are optional for containerized deployment.
How do I configure the server?
Configuration is loaded from environment variables prefixed with JIRA_MCP_ (highest priority), a config.yaml file, or application defaults. Required vars: JIRA_MCP_JIRA_URL, JIRA_MCP_JIRA_USER_EMAIL, JIRA_MCP_JIRA_API_TOKEN.
What API endpoints are available?
POST /create_jira_issue, POST /search_jira_issues, GET /jira_issue/{issueKey}, and GET /jira_epic/{epicKey}/issues (the Epic endpoint requires the JIRA_MCP_EPIC_LINK_FIELD_ID config).
How do I run the server with Docker?
Build the Docker image with make docker-build, create a .env file in the server directory with JIRA_MCP_ environment variables, then run make docker-run (which uses docker-compose up -d). To stop, run docker-compose down.
Where is my API token stored?
Never commit the token to version control. Use environment variables or a secure secrets manager. In Docker, store it in a .env file (excluded from Git) or inject it at runtime.
ēę¬ę§å¶ åē±»äøēę“å¤ MCP ęå”åØ

GitLab
modelcontextprotocolModel Context Protocol Servers
Atlassian Jira MCP Server
aashariNode.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.

Github
modelcontextprotocolModel Context Protocol Servers
Git MCP Server
cyanheadsA Git MCP server for AI agents. STDIO & Streamable HTTP.
GitHub MCP Server Extension for Zed
LoamStudiosA GitHub MCP Server extension for Zed
čÆč®ŗ