Atlassian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Base URL of Jira Server/Data Center, e.g. https://jira.example.com | |
| JIRA_USERNAME | Yes | Jira username for Basic authentication | |
| CONFLUENCE_URL | Yes | Base URL of Confluence Server/Data Center, e.g. https://confluence.example.com | |
| JIRA_API_TOKEN | Yes | Jira API token or password for Basic authentication | |
| CONFLUENCE_USERNAME | Yes | Confluence username (required for configuration although not used in Bearer authentication) | |
| CONFLUENCE_API_TOKEN | Yes | Confluence personal access token for Bearer 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_search_issuesA | Поиск задач Jira по JQL-запросу |
| jira_get_issueA | Get Jira issue details including parent, subtasks, issue links and remote links |
| jira_create_issueB | Создать новую задачу в Jira |
| jira_update_issueA | Обновить существующую задачу в Jira |
| jira_list_projectsA | Получить список всех проектов Jira |
| jira_add_commentB | Добавить комментарий к задаче Jira |
| jira_get_commentsB | Получить список комментариев к задаче Jira |
| confluence_search_pagesB | Search Confluence pages with CQL and return page IDs and URLs |
| confluence_get_pageC | Получить содержимое страницы Confluence по её ID |
| confluence_create_pageA | Создать новую страницу в Confluence (формат ADF) |
| confluence_update_pageC | Обновить существующую страницу Confluence |
| confluence_list_spacesA | Получить список всех пространств Confluence |
| confluence_find_pages_for_issueA | Find Confluence pages for a Jira issue using remote links, then CQL title search |
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 13 tools
Each tool targets a distinct resource and action, with clear separation between Jira and Confluence tools. Potential overlap between search tools is resolved by context: jira_search_issues searches issues, confluence_search_pages searches pages, and confluence_find_pages_for_issue links issues to pages.
All tool names follow a consistent snake_case pattern with a product prefix and a verb_noun structure, e.g., jira_create_issue, confluence_get_page. Minor verb variation (search, list, find) is still predictable and does not create confusion.
With 13 tools covering both Jira and Confluence core operations, the set is well-scoped for an Atlassian integration. Each tool addresses a meaningful operation without unnecessary bloat or duplication.
The server covers essential Jira issue and Confluence page workflows, including search, read, create, update, and comments. Minor gaps exist such as delete operations, Jira transitions, and Confluence page deletion, but core integration workflows are not blocked.