Jira/Confluence Team Lead MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | No | Base URL for Jira. Set together with CONFLUENCE_BASE_URL when Jira and Confluence are on different hosts. | |
| ATLASSIAN_EMAIL | Yes | Your Atlassian account email address. | |
| ATLASSIAN_BASE_URL | No | Base URL for your Atlassian instance (e.g., https://your-domain.atlassian.net). Used for both Jira and Confluence when they are on the same host. | |
| ATLASSIAN_API_TOKEN | Yes | API token created at https://id.atlassian.com/manage-profile/security/api-tokens | |
| ATLASSIAN_CA_BUNDLE | No | Path to a CA bundle file for corporate internal TLS chains. | |
| CONFLUENCE_BASE_URL | No | Base URL for Confluence. Set together with JIRA_BASE_URL when Jira and Confluence are on different hosts. | |
| ATLASSIAN_DEPLOYMENT | No | Deployment type: 'auto', 'cloud', or 'data-center'. Leave as 'auto' unless the URL doesn't give it away. | auto |
| ATLASSIAN_VERIFY_SSL | No | Set to 'false' to disable SSL certificate verification. Prefer setting ATLASSIAN_CA_BUNDLE instead. | true |
| REFINEMENT_DOD_LABELS | No | The team's Definition of Done labels. | |
| REFINEMENT_DOR_LABELS | No | The team's Definition of Ready labels. | |
| JIRA_STORY_POINTS_FIELD | No | Custom field ID for story points. If not set, auto-discovery looks for 'Story Points' or 'Story point estimate'. |
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 |
|---|---|
| check_connectionA | Verify Jira and Confluence credentials and show the resolved configuration (base URLs, deployment flavour, discovered story points field, defaults). Run this first on a new instance. |
| list_sprintsB | List sprints on a board so you can pick sprint ids. state is one of active, closed, future (comma-separate for several). |
| get_sprint_issuesA | Issues in a sprint, optionally filtered by status name (e.g. 'Needs Refinement') or status category (new/indeterminate/done). Returns key, summary, assignee, story points and status. Set publish=true to write the result to Confluence. |
| get_developer_sprint_historyA | Multi-sprint rollup grouped by developer (2-5 sprints is the useful range). Uses the Jira changelog, so time-in-status, cycle time and lead time are real, not inferred from current status. One flat table with developer as a column, so it can be sorted and filtered. |
| get_refinement_readiness_reportA | Weekly refinement readiness report: stories missing an estimate or missing DOR/DOD labels, plus a suggested attendee list for the refinement meeting. scope is 'backlog' (board backlog) or 'sprint'. checks defaults to estimate,dor,dod — add 'description' to also flag stories with no description. |
| publish_confluence_pageA | Create or overwrite a Confluence page. body must be Confluence storage format (XHTML) — pass the |
| check_confluence_capabilitiesB | Report what this Confluence instance supports for interactive tables: deployment flavour and whether the Table Filter, Charts & Spreadsheet app is installed. Use before choosing table_style. |
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 7 tools
Each tool has a clear focus: connection verification, sprint listing, sprint issue retrieval, developer history, readiness report, Confluence publishing, and Confluence capability checking. The two 'check' tools are distinct in scope (credentials/config vs. instance capabilities), and the three 'get' tools serve different analytical purposes. Minor potential confusion between get_sprint_issues and get_refinement_readiness_report, but their descriptions clarify.
All tool names follow a consistent verb_noun pattern with snake_case (check_connection, list_sprints, get_sprint_issues, etc.). Verbs are consistent with actions: check for verification, list for enumeration, get for retrieval, publish for writing. No mixed conventions.
Seven tools is well-scoped for a Jira/Confluence reporting server. Each tool fills a distinct role: setup verification, sprint navigation, issue analysis, developer performance, readiness reporting, publishing, and format capability detection. No redundancy or bloat.
The tool set covers the full reporting workflow: verify connection, find sprints, analyze issues by sprint or developer, generate readiness report, and publish results to Confluence. Minor gaps like listing boards or projects are handled through configuration defaults rather than requiring tools. No tool for arbitrary JQL queries, but not necessary for the stated purpose.