mcpField
J
Jira communication server MCP Server

Jira communication server MCP Server

Local
github.com/Raghvendra2420Version Control0Updated 77w ago
Repository

About Jira communication server MCP Server

A TypeScript MCP server for operating Jira through tools. It covers JQL queries, ticket management, and common project and status listings.

Key features

  1. 01Run JQL queries
  2. 02Create, edit, and delete tickets
  3. 03Assign tickets and find assignable users
  4. 04List projects and ticket statuses
  5. 05Attach files to tickets

Use cases

  1. 01Find Jira issues with JQL
  2. 02Create or update project tickets
  3. 03Assign tickets and attach image URLs

MCP support

As an MCP server, it exposes Jira query and ticket-management tools to MCP clients.

#jira#communication#mcp-server

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Jira communication server MCP Server

Talk to Jira

Jira Server MCP server

This is a TypeScript-based MCP server that provides tools to interact with Jira. It demonstrates core MCP concepts by providing:

  • Tools for executing JQL queries
  • Tools for creating, editing, and deleting Jira tickets
  • Tools for listing Jira projects and statuses

Features

Jira Tools

execute_jql
  • Purpose: Run a JQL query.
  • Parameters: jql, number_of_results (default: 1).
get_only_ticket_name_and_description
  • Purpose: Fetch ticket name and description.
  • Parameters: jql, number_of_results (default: 1).
create_ticket
  • Purpose: Create a Jira ticket.
  • Parameters: project.key, summary, description, issuetype.name, parent (optional).
list_projects
  • Purpose: List Jira projects.
  • Parameters: number_of_results (default: 1).
delete_ticket
  • Purpose: Delete a ticket.
  • Parameters: issueIdOrKey.
edit_ticket
  • Purpose: Modify a ticket.
  • Parameters: issueIdOrKey, summary (optional), description (optional), labels (optional), parent (optional).
get_all_statuses
  • Purpose: Retrieve all statuses.
  • Parameters: number_of_results (default: 1).
assign_ticket
  • Purpose: Assign a ticket to a user.
  • Parameters: accountId, issueIdOrKey.
query_assignable
  • Purpose: Find assignable users in a project.
  • Parameters: project_key.
add_attachment
  • Purpose: Add an attachment to a ticket.
  • Parameters: issueIdOrKey, imageUrl.

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "Jira communication server": {
      "command": "node",
      "args": [
        "/PATH_TO_THE_PROJECT/build/index.js"
      ],
      "env": {
        "JIRA_URL": "https://XXXXXXXX.atlassian.net",
        "JIRA_API_MAIL": "Your email",
        "JIRA_API_KEY": "KEY_FROM : https://id.atlassian.com/manage-profile/security/api-tokens"
      }
    }
  }
}
Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.