Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Your Jira instance URL (e.g., https://XXXXXXXX.atlassian.net) | |
| JIRA_API_KEY | Yes | Your Jira API token from https://id.atlassian.com/manage-profile/security/api-tokens | |
| JIRA_API_MAIL | Yes | Your email address for Jira API authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_jqlC | Execute a JQL query on Jira on the api /rest/api/3/search/jql. Do not use markdown in your query. |
| get_only_ticket_name_and_descriptionC | Get the name and description of the requested tickets on the api /rest/api/3/search/jql. Do not use markdown in your query. |
| create_ticketC | Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field. |
| list_projectsC | List all the projects on Jira on the api /rest/api/3/project. Do not use markdown in your query. |
| delete_ticketC | Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query. |
| edit_ticketC | Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in any field. |
| get_all_statusesC | Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your query. |
| assign_ticketB | Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use markdown in your query. |
| 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. |
| 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. |
| add_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting specific Jira operations like create, edit, delete, assign, query, and list. However, 'execute_jql' and 'get_only_ticket_name_and_description' both query tickets via JQL, creating some overlap that could cause confusion, though their descriptions clarify different output focuses.
All tool names follow a consistent verb_noun pattern with snake_case throughout, such as 'create_ticket', 'assign_ticket', and 'list_projects'. This predictability makes it easy for agents to understand and navigate the tool set without naming conflicts.
With 11 tools, the count is well-scoped for a Jira server, covering core operations like ticket management, attachments, queries, and project listing. Each tool appears to serve a specific function without unnecessary bloat, fitting typical server tool ranges.
The tool set provides good coverage for Jira workflows, including CRUD operations for tickets, assignment, attachments, and project/status queries. Minor gaps exist, such as missing tools for comments, transitions, or watchers, but core functionalities are present and agents can likely work around these omissions.