Jira Communication Server
Provides tools for executing JQL queries, creating, editing, deleting Jira tickets, listing projects and statuses, assigning tickets, finding assignable users, and adding attachments.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Jira Communication Server List all Jira projects"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Jira 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
Related MCP server: Jira MCP Integration
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 installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchInstallation
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 inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Available Tools
11 toolsadd_attachment_from_confluenceC
Add an attachment to a ticket on Jira from a Confluence page by its name on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query.
Inputs: pageId (required), issueIdOrKey (required), attachmentName (required).
add_attachment_from_public_urlA
Add an attachment from a public url to a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query.
Inputs: imageUrl (required), issueIdOrKey (required).
assign_ticketB
Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use markdown in your query.
Inputs: accountId (required), issueIdOrKey (required).
create_ticketC
Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field.
Inputs: project (required), summary (required), issuetype (required), description (required), +1 more.
delete_ticketC
Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query.
Inputs: issueIdOrKey (required).
edit_ticketC
Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in any field.
Inputs: issueIdOrKey (required), labels, parent, summary, +1 more.
execute_jqlC
Execute a JQL query on Jira on the api /rest/api/3/search. Do not use markdown in your query.
Inputs: jql (required), number_of_results.
get_all_statusesC
Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your query.
Inputs: number_of_results.
get_only_ticket_name_and_descriptionB
Get the name and description of the requested tickets on the api /rest/api/3/search. Do not use markdown in your query.
Inputs: jql (required), number_of_results.
list_projectsC
List all the projects on Jira on the api /rest/api/3/project. Do not use markdown in your query.
Inputs: number_of_results.
query_assignableC
Query assignables to a ticket on Jira on the api /rest/api/3/user/assignable/search?project={project-name}. Do not use markdown in your query.
Inputs: project_key (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
All tools have clearly distinct purposes: CRUD tickets, two attachment sources, project/status listing, JQL search, ticket retrieval by name&desc, assignee query, and assignment. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case, with verbs like add, assign, create, delete, edit, execute, get, list, query. No mixing of styles.
11 tools is well-scoped for a Jira server, covering essential operations without being bloated or insufficient.
Covers major CRUD for tickets, search, projects, statuses, assignments, and attachments. Missing a generic 'get_ticket' for full details and some lifecycle features like transitions or comment management, but still quite complete.
Maintenance
Related MCP Connectors
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
Manage dillie projects, tasks, and sprints; look up members and search platform documentation.
Task manager your agent can fully operate: boards, tasks, sprints, roles, worklogs, day planner.
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.610 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.-
- AlicenseNot gradedqualityBmaintenanceProvides Jira Cloud integration for AI agents, enabling them to search issues with JQL, retrieve detailed issue information, and create new tickets. It supports multiple Jira configurations and provides tools for managing attachments and comments through natural language.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to manage Jira projects and issues using natural language, including creating, updating, searching issues, managing sprints, and more via the Jira API.361,677 npm1MIT