Atlassian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira email | |
| JIRA_DOMAIN | Yes | Your Jira domain (e.g., your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your Jira API token | |
| JIRA_CLIENT_ID | No | Optional Jira OAuth client ID | |
| CONFLUENCE_EMAIL | Yes | Your Confluence email | |
| MCP_SNAPSHOT_DIR | No | Snapshot directory (default: ~/.atlassian-mcp-snapshots) | |
| CONFLUENCE_DOMAIN | Yes | Your Confluence domain (e.g., your-domain.atlassian.net) | |
| BITBUCKET_USERNAME | Yes | Your Bitbucket username | |
| JIRA_CLIENT_SECRET | No | Optional Jira OAuth client secret | |
| BITBUCKET_API_TOKEN | Yes | Your Bitbucket API token | |
| BITBUCKET_WORKSPACE | Yes | Your Bitbucket workspace | |
| CONFLUENCE_API_TOKEN | Yes | Your Confluence API token | |
| MCP_SNAPSHOTS_ENABLED | No | Enable snapshot safety net (default: true) | |
| MCP_SNAPSHOT_RETENTION_DAYS | No | Snapshot retention in days (default: 30) |
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_search_pagesA | Search Confluence pages by text query (CQL). Returns matching pages; the |
| confluence_get_pageB | Get a specific Confluence page by ID. The |
| confluence_create_pageA | Create a new Confluence page. The |
| confluence_update_pageA | Update an existing Confluence page. The |
| confluence_get_spacesC | Get list of Confluence spaces |
| confluence_get_pages_by_spaceA | Get pages from a specific Confluence space. The |
| confluence_get_attachmentsB | Get all attachments for a Confluence page |
| confluence_add_attachmentB | Add an attachment to a Confluence page. Provide either filePath (local file) or fileContent (base64). |
| confluence_delete_attachmentC | Delete an attachment from a Confluence page |
| confluence_embed_imageA | NOT SUPPORTED in this version. Inline image embedding requires the Atlassian Media API (ADF media nodes) and is not implemented. Use confluence_add_attachment to upload the file and reference it from the Confluence UI. Calling this tool will return an error. |
| confluence_get_commentsA | Get comments for a Confluence page. Returns both footer (page-level) and inline (text-anchored) comments by default. Each comment carries a |
| confluence_add_commentB | Add a comment to a Confluence page |
| confluence_update_commentB | Update an existing comment on a Confluence page |
| confluence_delete_commentB | Delete a comment from a Confluence page |
| confluence_get_page_childrenA | Get child pages of a Confluence page. v2 returns child summaries only — |
| confluence_get_labelsA | Get all labels on a Confluence page |
| confluence_add_labelsB | Add labels to a Confluence page |
| confluence_remove_labelB | Remove a label from a Confluence page |
| confluence_delete_pageB | Delete a Confluence page |
| confluence_get_page_historyB | Get version history for a Confluence page |
| jira_search_issuesA | Search Jira issues with flexible filtering. Use individual filters (assignee, status, project, labels) or provide raw JQL for advanced queries. |
| jira_get_issueA | Get a specific Jira issue by key. Optionally specify which fields to return. |
| jira_create_issueC | Create a new Jira issue with support for custom fields including due dates |
| jira_update_issueB | Update an existing Jira issue. Supports standard fields and custom fields (use jira_get_fields to discover field IDs). |
| jira_add_commentB | Add a comment to a Jira issue |
| jira_get_commentsC | Get all comments for a Jira issue |
| jira_update_commentB | Update an existing comment on a Jira issue |
| jira_delete_commentB | Delete a comment from a Jira issue |
| jira_get_projectsA | Get list of Jira projects |
| jira_get_issue_transitionsB | Get available transitions for a Jira issue |
| jira_transition_issueB | Transition a Jira issue to a different status with smart field handling |
| jira_transition_issue_interactiveA | Transition a Jira issue with automatic field suggestion and validation |
| jira_get_attachmentsB | Get all attachments for a Jira issue |
| jira_add_attachmentC | Add an attachment to a Jira issue |
| jira_delete_attachmentB | Delete an attachment from a Jira issue |
| jira_get_issue_linksB | Get all issue links for a Jira issue |
| jira_create_issue_linkB | Create a link between two Jira issues |
| jira_delete_issue_linkB | Delete a link between Jira issues |
| jira_get_link_typesA | Get all available issue link types in Jira |
| jira_get_worklogsA | Get all work logs (time tracking entries) for a Jira issue |
| jira_add_worklogB | Add a work log (time spent) to a Jira issue |
| jira_update_worklogC | Update an existing work log entry |
| jira_delete_worklogA | Delete a work log entry from a Jira issue |
| jira_get_watchersB | Get all watchers for a Jira issue |
| jira_add_watcherC | Add a watcher to a Jira issue |
| jira_remove_watcherB | Remove a watcher from a Jira issue |
| jira_get_subtasksC | Get all sub-tasks for a Jira issue |
| jira_create_subtaskB | Create a sub-task under a parent Jira issue |
| jira_get_issue_historyB | Get complete change history for a Jira issue |
| jira_get_fieldsA | Search and discover available Jira fields. Use this to find field IDs (e.g. search "sprint" to find the Sprint custom field ID) for use with jira_get_issue and jira_search_issues fields parameter. |
| jira_get_labelsA | Get available labels in Jira. Optionally filter by a search query. |
| jira_add_labelsB | Add labels to a Jira issue |
| jira_remove_labelsB | Remove labels from a Jira issue |
| jira_get_agile_boardsB | Get Jira agile boards. Optionally filter by name, type (scrum/kanban), or project. |
| jira_get_board_issuesC | Get all issues on a Jira agile board |
| jira_get_sprintsB | Get sprints for a Jira agile board |
| jira_get_sprint_issuesB | Get all issues in a specific sprint |
| jira_move_issues_to_sprintB | Move one or more issues to a sprint |
| jira_batch_create_issuesB | Create multiple Jira issues in a single request (max 50) |
| jira_get_dev_statusB | Get development information (PRs, branches, commits) linked to a Jira issue |
| jira_delete_issueB | Delete a Jira issue. Optionally delete its subtasks. |
| jira_lookup_userA | Look up Jira users by name or email address. Returns account IDs needed for assignee, watcher, and other user fields. |
| jira_get_issue_typesA | Get available issue types for a Jira project (e.g., Bug, Story, Task, Epic, Sub-task) |
| jira_create_sprintB | Create a new sprint on a Jira agile board |
| jira_update_sprintB | Update an existing sprint (name, dates, state, goal) |
| jira_get_project_versionsA | Get all versions (releases) for a Jira project |
| jira_create_versionC | Create a new version (release) in a Jira project |
| jira_update_versionC | Update an existing version (release) in Jira |
| jira_link_to_epicA | Link an issue to an epic. Works with both next-gen (parent field) and classic (Epic Link field) projects. |
| bitbucket_get_repositoriesB | Get list of Bitbucket repositories in workspace |
| bitbucket_get_repositoryA | Get details of a specific Bitbucket repository |
| bitbucket_create_repositoryB | Create a new Bitbucket repository |
| bitbucket_get_pull_requestsC | Get pull requests for a repository |
| bitbucket_get_pull_requestB | Get details of a specific pull request |
| bitbucket_create_pull_requestB | Create a new pull request |
| bitbucket_update_pull_requestB | Update an existing pull request (title, description, or destination branch). At least one of title, description, or destinationBranch must be provided. |
| bitbucket_get_branchesB | Get branches for a repository |
| bitbucket_get_commitsC | Get commits for a repository |
| bitbucket_get_issuesC | Get issues for a repository |
| bitbucket_create_issueB | Create a new issue in a repository |
| bitbucket_get_pr_commentsB | Get all comments for a Bitbucket pull request |
| bitbucket_add_pr_commentA | Add a comment to a Bitbucket pull request. Supports both general and inline (file/line) comments. |
| bitbucket_update_pr_commentA | Update an existing comment on a Bitbucket pull request |
| bitbucket_delete_pr_commentB | Delete a comment from a Bitbucket pull request |
| bitbucket_resolve_pr_commentB | Resolve a comment on a Bitbucket pull request |
| bitbucket_unresolve_pr_commentB | Unresolve (reopen) a comment on a Bitbucket pull request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jagadeesh52423/ConfluenceMcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server