MCP Atlassian Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | The URL of your Jira instance (e.g., https://your-company.atlassian.net or https://jira.your-company.com) | |
| MCP_VERBOSE | No | Set to 'true' to enable debug logging | |
| ENABLED_TOOLS | No | Comma-separated list of specific tools to enable (e.g., confluence_search,jira_get_issue) | |
| JIRA_USERNAME | No | Your Jira username (email) for cloud API token authentication | |
| CONFLUENCE_URL | No | The URL of your Confluence instance (e.g., https://your-company.atlassian.net/wiki or https://confluence.your-company.com) | |
| JIRA_API_TOKEN | No | Your Jira API token for cloud authentication | |
| READ_ONLY_MODE | No | Set to 'true' to disable write operations | |
| CONFLUENCE_USERNAME | No | Your Confluence username (email) for cloud API token authentication | |
| JIRA_PERSONAL_TOKEN | No | Your Jira Personal Access Token for server/Data Center authentication | |
| CONFLUENCE_API_TOKEN | No | Your Confluence API token for cloud authentication | |
| JIRA_PROJECTS_FILTER | No | Comma-separated list of Jira project keys to restrict access | |
| CONFLUENCE_SPACES_FILTER | No | Comma-separated list of Confluence space keys to restrict access | |
| CONFLUENCE_PERSONAL_TOKEN | No | Your Confluence Personal Access Token for server/Data Center 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
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 |
|---|---|
| confluence_searchC | Search for content in Confluence using CQL (Confluence Query Language) |
| confluence_get_pageC | Get a specific Confluence page by ID |
| confluence_create_pageC | Create a new page in Confluence |
| confluence_update_pageB | Update an existing Confluence page |
| confluence_get_spacesB | Get a list of spaces in Confluence |
| jira_search_issuesC | Search for issues in Jira using JQL (Jira Query Language) |
| jira_get_issueB | Get a specific Jira issue by key |
| jira_create_issueB | Create a new issue in Jira |
| jira_update_issueC | Update an existing Jira issue |
| jira_add_commentC | Add a comment to a Jira issue |
| jira_get_projectsB | Get a list of projects in Jira |
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
All tools have clearly distinct purposes, separated by product prefix (confluence_ vs jira_) and action verbs (search, get, create, update, add, get list). No ambiguity between tools.
Naming follows a uniform snake_case pattern: <product>_<verb>_<noun>. All Confluence tools start with 'confluence_' and Jira tools with 'jira_', with consistent verb choice across the set.
11 tools is well-scoped for covering both Confluence and Jira core operations. Neither too few nor too many, each tool serves a distinct and needed function.
The set covers search, create, read, and update for pages and issues, plus listing spaces and projects. However, it lacks delete operations for both Confluence and Jira, and misses common features like Jira transitions or Confluence attachments, leaving notable gaps.