Jira communication server MCP Server
LocalAbout Jira communication server MCP Server
Jira communication server MCP Server is a TypeScript MCP server that exposes tools for working with Jira. The README describes it as a test project that demonstrates core MCP concepts.
Key features
- 01Run JQL queries against Jira
- 02Create, edit and delete tickets
- 03List projects, statuses and assignable users
- 04Attach files from public URLs or Confluence
Use cases
- 01Querying and organizing Jira tickets from an AI assistant
- 02Viewing or updating tickets from Claude Desktop
- 03Adding Confluence page attachments to tickets
MCP support
This is an MCP server that exposes several Jira operation tools to MCP clients, configured for use with Claude Desktop.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEJira communication server MCP Server
Talk to Jira
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_from_public_url
- Purpose: Add an attachment from a public URL to a ticket.
- Parameters:
issueIdOrKey,imageUrl.
add_attachment_from_confluence
- Purpose: Add an attachment from a Confluence page to a ticket.
- Parameters:
issueIdOrKey,pageId,attachmentName.
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
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.