This Jira MCP Server provides a modular set of tools to query and interact with Jira Cloud from an MCP-enabled agent or workflow. It exposes tools to list boards, fetch issues for a board, add comments to issues, retrieve the currently authenticated user, search for users, and obtain server information. Each tool is designed to be invoked via the MCP Inspector or through an MCP-compatible agent, enabling seamless integration with AI reasoning or automation pipelines. You can invoke the available tools by using the inspector CLI and pointing to the Jira MCP Server as the tool source, then selecting the appropriate tool name and arguments. The server handles communication with Jira Cloud using the configured base URL, user email, and API token.

Common workflows include listing all boards to select a board for further actions, retrieving the user’s own issues for a specific board, and adding comments to issues for collaboration or automation notes. You can also query current user information or search for users by login, email, or display name to resolve user references in automation tasks. Use get_server_info to verify connectivity and server time when needed.

Prerequisites:

• Node.js 18+ installed on your system
• Access to a Jira Cloud instance with an API token

Installation steps:

1. Ensure Node.js is installed and accessible in your shell.
2. Install the MCP server from npm or use npx directly (no global install required):
   • If you want to run with npx: npx -y @ahmetbarut/jira-mcp-server
   • Or clone the repository and install dependencies locally: git clone https://github.com/ahmetbarut/jira-mcp.git cd jira-mcp-server npm install
3. Set environment variables (JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN) in your shell or a .env file.
4. Build the project if you are running from source: npm run build
5. Run the server: jira-mcp-server

   or with npx (no global install): npx -y @ahmetbarut/jira-mcp-server

Environment variables are required to authenticate to Jira Cloud:

• JIRA_BASE_URL: Your Jira Cloud base URL (e.g., https://your-domain.atlassian.net)
• JIRA_EMAIL: The account email associated with your Jira API token
• JIRA_API_TOKEN: A Jira API token generated in your Atlassian account

Tips:

• When using npx, dependencies are downloaded on first run; the initial invocation may take a few seconds.
• If you encounter authentication errors, double-check that the API token has the correct scopes and that the base URL is reachable from your environment.
• Use the MCP Inspector to interact with tools; common tool names include get_boards, get_issues, add_comment_to_issue, get_current_user_info, search_user, and get_server_info.
• For production deployments, consider setting environment variables through your deployment platform’s secret management instead of in plaintext files.