Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | The Jira instance URL, e.g. https://clarodigital.atlassian.net | |
| JIRA_EMAIL | Yes | Your Jira email address | |
| JIRA_API_TOKEN | Yes | Your Jira API token |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_my_tasksA | List all unresolved tasks assigned to current user |
| list_my_board_tasksA | List all tasks assigned to current user in CCOE project board (Atlantis P&D) - Use terminal commands for board-specific searches |
| list_subtasksB | List all subtasks assigned to current user |
| list_sprint_activeB | List all tasks in active sprint assigned to current user |
| list_in_developmentC | List tasks currently in development |
| list_projectsA | List all available Jira projects |
| custom_queryC | Execute custom JQL query |
| add_worklogB | Add time log (worklog) to an issue or subtask |
| list_worklogsA | List all worklogs for an issue |
| add_commentB | Add a comment to an issue or subtask for traceability |
| list_commentsA | List all comments for an issue |
| get_project_issue_typesA | Get available issue types for a project (useful for finding issue type IDs) |
| get_issue_custom_fieldsA | Get custom field values from an existing issue (useful for discovering field IDs) |
| create_issueA | Create a new Jira issue with specified fields. For CCOE project, required fields (3F and Tipo) are auto-filled with defaults if not provided. Use ccoe3F and ccoeType parameters for easy selection, or customFields for full control. |
| update_issue_statusA | Update the status of a Jira issue (transition workflow) |
| update_issueB | Update fields of an existing Jira issue |
| list_attachmentsA | List all attachments for a Jira issue |
| add_attachmentA | Add attachment to a Jira issue (provide file path) |
| search_confluenceB | Search Confluence pages using CQL (Confluence Query Language) |
| get_confluence_pageB | Get the content of a Confluence page by ID |
| create_confluence_pageB | Create a new Confluence page in a specific space |
| update_confluence_pageB | Update the content of an existing Confluence page |
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 22 tools
Several tools overlap in purpose: list_my_tasks, list_subtasks, list_sprint_active, list_in_development, and list_my_board_tasks all list tasks assigned to the current user with only subtle filter differences. custom_query can also replicate these searches, making tool boundaries unclear.
Most tools follow a consistent verb_noun snake_case pattern (e.g., list_projects, create_issue, add_comment, get_confluence_page). Minor deviations include custom_query (not verb_noun) and update_issue_status (three-part), but the overall style is predictable.
With 22 tools, the server is on the heavier side for a Jira+Confluence integration. While not extreme, the count falls in the 16-25 range that feels somewhat bloated but still manageable for the scope.
Core workflows are covered: issue creation/update/status, comments, worklogs, attachments, JQL queries, and Confluence get/search/create/update. However, there is no direct get_issue by key, no delete operations for issues/comments/worklogs/attachments, and no Confluence space listing, leaving notable gaps that require workarounds.