mcp-jira-confluence-corp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | Base URL of your Jira instance | |
| JIRA_TOKEN | No | Token for Jira Basic Auth (alternative to PAT) | |
| JIRA_USERNAME | No | Username for Jira Basic Auth (alternative to PAT) | |
| CONFLUENCE_URL | No | Base URL of your Confluence instance | |
| MCP_BYPASS_DOMAINS | No | Comma-separated list of internal domains to bypass any proxy. Supports wildcards. | |
| JIRA_PERSONAL_TOKEN | No | Personal Access Token for Jira | |
| CONFLUENCE_PERSONAL_TOKEN | No | Personal Access Token for Confluence |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_get_issueA | Fetch a Jira issue by key, returning its core fields and description. Args:
params: Validated :class: Returns: A markdown summary (default) or JSON dump of the full Jira issue payload. On error, a human-readable error string. |
| jira_search_issuesA | Search Jira issues with a JQL query. Supports pagination via |
| jira_get_issue_commentsA | Return all comments on a Jira issue. |
| jira_get_issue_transitionsA | List workflow transitions currently available for an issue. |
| jira_get_issue_changelogA | Return the change history of a Jira issue. |
| jira_list_projectsB | List all accessible Jira projects. |
| jira_get_projectA | Get details of a Jira project by key. |
| jira_get_userA | Get a Jira user profile by username or accountId. |
| jira_field_mapA | Build a mapping table for Jira field IDs, names, schemas, and editability. With no arguments, returns the global field catalog. Supplying
|
| jira_get_my_issuesB | List issues currently assigned to the authenticated user. |
| jira_summarize_issueA | One-shot comprehensive summary: issue fields + comments + changelog + transitions. Use this instead of calling four separate tools when you need full context on an issue. |
| jira_list_agile_boardsA | List Scrum/Kanban boards, optionally filtered by project or type. |
| jira_list_board_sprintsA | List sprints for an agile board, filtered by state. |
| jira_list_sprint_issuesB | List all issues in a given sprint. |
| jira_create_issueA | Create a new Jira issue. Required: |
| jira_update_issueB | Update fields on an existing Jira issue. |
| jira_add_commentC | Add a comment to a Jira issue. |
| jira_transition_issueA | Move a Jira issue through its workflow by transition name. Transition names are case-insensitive. If the name doesn't match an available transition, the error message will list the valid options. |
| jira_assign_issueB | Assign or unassign a Jira issue. Pass |
| confluence_get_pageA | Fetch a Confluence page by ID. Returns the page metadata plus its body in Confluence Storage Format (XHTML) by default. |
| confluence_get_page_by_titleB | Fetch a Confluence page by exact title within a space. |
| confluence_searchA | Search Confluence using Confluence Query Language (CQL). Example queries:
- |
| confluence_get_page_childrenB | List child pages of a Confluence page. |
| confluence_get_page_commentsB | List comments on a Confluence page. |
| confluence_get_page_labelsA | List labels applied to a Confluence page. |
| confluence_list_spacesA | List Confluence spaces, optionally filtered by type ('global'/'personal'). |
| confluence_get_page_historyB | Return version history info for a Confluence page. |
| confluence_get_page_attachmentsA | List attachments on a Confluence page. |
| confluence_create_pageB | Create a new Confluence page.
|
| confluence_update_pageA | Update an existing Confluence page (full replacement of body). |
| confluence_add_commentC | Add a comment to a Confluence page. |
| confluence_add_labelC | Add a label to a Confluence page. |
| confluence_remove_labelB | Remove a label from a Confluence page. |
| jira_extract_linksA | Find every Confluence, Git, or other URL referenced by a Jira issue. Scans the issue's description, optionally its comments, and (optionally)
Jira's remote-issue-link entries. Returns links grouped by category:
Use cases: - "What design docs are linked from PROJ-123?" - "Which repos does this story touch?" |
| jira_daily_standup_summaryA | Compile a daily-standup-style picture of a sprint in one call. Returns: sprint metadata, counts by status, blockers (issues with the
'blocked' label or 'Blocked' status), and assignee workload.
Either |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| confluence_create_release_notes | Draft a Confluence release-notes page from a set of Jira issues. Provide fix_version (and optionally space_key/parent_id) and the LLM will fetch the issues, group them, and produce a Storage-Format body ready for confluence_create_page. |
| confluence_document_feature | Draft a Confluence feature documentation page from a Jira epic or story. The LLM will pull issue context, related links, and produce a structured page ready to publish. |
| confluence_audit_page | Audit a Confluence page for staleness, broken links, missing metadata, and orphan child pages. Returns a written report. |
| confluence_summarize_space | Survey a Confluence space and produce a structured summary: number of pages, recently updated, stale pages, top contributors. |
| jira_sprint_report | Produce a sprint review / retro-ready report for a given sprint, with completed vs. spillover work, blockers, and per-assignee load. |
| jira_triage_my_issues | Triage the user's own assigned issues: identify what to work on next, what is stale, and what should be re-prioritised. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 35 tools
Tools are clearly separated by service prefix (jira_ vs confluence_), and within each service, every tool has a distinct purpose with no overlaps. For example, jira_get_issue retrieves an issue while jira_summarize_issue provides a comprehensive view, but the descriptions clarify their different scopes.
All tool names follow a consistent snake_case pattern with a service prefix and verb_noun structure (e.g., jira_create_issue, confluence_get_page). There are no deviations or mixed conventions.
With 35 tools covering both Jira and Confluence, the count is on the higher side but justified by the breadth of functionality. Each tool serves a clear purpose and there is no obvious bloat, though a few tools could potentially be combined (e.g., jira_get_issue and jira_get_issue_changelog are separate but jira_summarize_issue consolidates similar data).
The tool surface covers core CRUD operations, search, comments, workflows, and administrative tasks for both Jira and Confluence. Notable minor gaps include missing delete operations (e.g., jira_delete_issue, confluence_delete_page), but these are not essential for common workflows. Overall, the set is comprehensive for most use cases.