MCP Atlassian Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_EMAIL | Yes | Your email address used for authentication | |
| ATLASSIAN_BASE_URL | Yes | The base URL of your Atlassian instance, e.g., https://yourdomain.atlassian.net | |
| ATLASSIAN_API_TOKEN | Yes | Your Atlassian 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 |
|---|---|
| get_confluence_current_userA | Get details of the authenticated Confluence user. Returns information about the current user including account ID, display name, email, and profile picture. |
| get_confluence_userA | Get details for a specific Confluence user by a unique identifier like username, account ID, or email. Returns user profile information. Use this tool when you are confident you can uniquely identify a user. |
| search_pages_by_user_involvementB | Search pages based on a user's involvement, such as being the creator or last modifier. Can filter by creator, last modifier, or both. |
| list_pages_created_by_userA | List all pages created by a specific user, with optional filtering by space or time range. |
| list_attachments_uploaded_by_userB | List all attachments uploaded by a specific user, with optional filtering by space. |
| read_confluence_pageA | Retrieves the content of a Confluence page. You can specify the page by its ID or by its title and space key. The content can be returned in raw storage format (XHTML) or converted to Markdown. Use this for quickly reading the text content of a page. |
| search_confluence_pagesB | Performs a search for Confluence pages using Confluence Query Language (CQL). This is useful for finding pages that match specific criteria. |
| list_confluence_spacesA | Lists all Confluence spaces that the user has permission to view. Can be filtered by type and status. |
| get_confluence_spaceA | Get details of a specific Confluence space by its key. Returns space information including name, type, status, and description. |
| list_attachments_on_pageC | Lists all attachments for a specific Confluence page. Can be filtered by filename or media type. |
| download_confluence_attachmentA | Downloads a specific Confluence attachment and returns its content as a base64-encoded string. This is useful for reading the content of files attached to a page. |
| upload_confluence_attachmentB | Upload a file attachment to a Confluence page. The file should be provided as a base64-encoded string. |
| get_page_with_attachmentsA | Performs a comprehensive download of a Confluence page, including its full content, metadata, and optionally, all of its attachments. Attachments are base64-encoded. Use this when you need the page content, metadata, and all associated attachments. |
| create_confluence_pageC | Creates a new page or blog post in a Confluence space. Content can be provided in Markdown or Confluence storage format (XHTML). |
| update_confluence_pageA | Updates an existing Confluence page. You must provide the page ID and its current version number to prevent conflicts. You can update the title, content, or both. |
| list_confluence_page_childrenA | List child pages under a given Confluence page. Returns a hierarchical list of direct child pages. |
| list_confluence_page_ancestorsA | Retrieve the parent hierarchy of a Confluence page. Returns the full ancestry path from root to the immediate parent. |
| add_confluence_commentA | Adds a comment to a Confluence page. Can also be used to reply to an existing comment. |
| find_confluence_usersA | Searches for Confluence users based on various criteria. This is useful for finding user details like account IDs when you have partial information or need to perform a broader search. Use this tool when you need to find users based on a query. |
| list_confluence_page_labelsB | Retrieves all labels for a specific Confluence page. |
| add_confluence_page_labelA | Adds one or more labels to a Confluence page. Labels are useful for organizing and categorizing content. |
| export_confluence_pageA | Exports a Confluence page to either HTML or Markdown format. All images in the page content are embedded directly into the exported file as base64 data, making it self-contained. Use this when you want to create a portable, self-contained file of a page. |
| get_my_recent_confluence_pagesA | List pages recently created or updated by the current user. Returns pages where you are the creator or last modifier. |
| get_confluence_pages_mentioning_meA | Search for pages that mention the current user. Returns pages where you have been @mentioned. |
| get_jira_current_userA | Get details of the authenticated Jira user. Returns information about the current user including account ID, display name, email, and avatar URLs. |
| get_jira_userA | Get details for a specific Jira user by username, account ID, or email. Returns user profile information. |
| search_issues_by_user_involvementB | Search for issues based on how a specific user is involved (assignee, reporter, creator, watcher, or any). Provides comprehensive filtering to find all issues a user is connected to. |
| list_issues_by_user_roleC | List issues where a user has a specific role (assignee, reporter, or creator). Includes date filtering for finding issues within specific time periods. |
| get_user_activity_historyC | Get a stream of recent user activity, such as issue comments, status changes, and field updates. Can filter by activity type and project. |
| get_user_time_trackingB | Retrieve time tracking work logs (worklogs) for a specific user. Shows all time entries logged by the user within a date range, useful for timesheet and worklog reporting. |
| read_jira_issueA | Retrieves detailed information about a specific Jira issue, including its fields, status, and transitions. Use this to get the full picture of a single issue. |
| search_jira_issuesB | Searches for Jira issues using Jira Query Language (JQL). This is the primary way to find issues that match specific criteria. |
| list_jira_projectsA | Lists all Jira projects that the user has permission to view. This is useful for discovering available projects to work with. |
| create_jira_issueA | Creates a new issue in a Jira project. You must specify the project, issue type, and a summary. Other fields like description, priority, and assignee are optional. |
| add_jira_commentA | Adds a comment to an existing Jira issue. You can also control the visibility of the comment. |
| list_agile_boardsA | List all accessible Agile boards (both Scrum and Kanban types). Can be filtered by project or board type to find specific boards. |
| list_sprints_for_boardA | List all sprints for a specific Agile board. Can filter by sprint state (active, closed, or future) to find current or historical sprints. |
| get_sprint_detailsA | Get comprehensive details about a specific sprint including its name, start/end dates, goals, and all issues included in the sprint. |
| get_my_current_sprint_issuesA | Get all issues assigned to you in the currently active sprint(s). Useful for daily standups or checking your current sprint workload. Can filter by specific board or project. |
| get_my_unresolved_issuesA | Get all unresolved issues currently assigned to you, organized by status and priority. Perfect for checking your backlog or identifying what needs attention. |
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 40 tools
Most tools are clearly scoped by product and resource type, and usage notes help distinguish read, get, export, and search variants. However, search_issues_by_user_involvement and list_issues_by_user_role overlap heavily, and search_pages_by_user_involvement vs list_pages_created_by_user creates ambiguity for user-based page lookup.
The majority of tools follow a consistent verb_noun pattern with product prefixes like get_confluence_, list_jira_, create_confluence_page, and search_jira_issues. Minor deviations such as get_page_with_attachments, get_my_recent_confluence_pages, and get_my_unresolved_issues break the pattern slightly.
With 40 tools, the server is well beyond the typical well-scoped range, even for a combined Confluence and Jira server. Many tools are narrow user-reporting or variation-on-a-theme operations, which makes the set feel bloated rather than curated.
The server covers broad read/search functionality across Confluence and Jira, plus page create/update, issue creation, comments, attachments, labels, spaces, users, and agile boards/sprunts. However, there are important lifecycle gaps: no update/transition/delete for Jira issues, no delete for Confluence pages/attachments/comments, and no comment update/delete.