db3-atlassian-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_USER | No | Your Jira user email. Required if not provided via .env file. | |
| JIRA_API_KEY | No | Your Atlassian API token. Required if not provided via .env file. | |
| JIRA_BASE_URL | No | Your Jira instance base URL (e.g., https://yourcompany.atlassian.net). Required if not provided via .env file. | |
| BITBUCKET_USER | No | Bitbucket user email. Optional. | |
| BITBUCKET_API_TOKEN | No | Bitbucket Cloud API token. Optional. | |
| BITBUCKET_WORKSPACE | No | Bitbucket workspace name (e.g., your-workspace). Optional. | |
| ENABLE_BITBUCKET_PR_TOOLS | No | Set to 'true' to enable additional Bitbucket PR tools (commits, diffs, comments, etc.). Optional, defaults to 'false'. | |
| ENABLE_BITBUCKET_ADMIN_TOOLS | No | Set to 'true' to enable Bitbucket admin tools (build statuses, pipelines, tasks, etc.). Optional, defaults to 'false'. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_create_fieldsA | List Jira fields available when creating a ticket, including IDs, names, required flags, schemas, and allowed values. |
| get_ticketA | Fetch a Jira ticket by key (e.g. INFOSEC-2239). Returns standard fields, description, and populated custom fields. |
| search_ticketsA | Search Jira tickets using JQL. Example: 'project = INFOSEC AND status = Open' |
| get_child_issuesA | Get all child/sub-task issues for a given parent ticket. |
| list_bitbucket_reposC | List Bitbucket Cloud repositories in a workspace. |
| get_bitbucket_repoC | Fetch Bitbucket Cloud repository metadata. |
| search_bitbucket_reposC | Search Bitbucket Cloud repositories by slug, name, or description. |
| list_bitbucket_branchesA | List Bitbucket Cloud branches for a repository, optionally filtered by name. |
| list_bitbucket_pull_requestsC | List Bitbucket Cloud pull requests for a repository. |
| get_bitbucket_pull_requestC | Fetch Bitbucket Cloud pull request details. |
| create_ticketB | Create a new Jira ticket. Optionally pass custom_fields for Jira customfield_* or other fields. |
| update_ticketA | Update a Jira ticket. Can change standard fields, custom_fields, transition status, and/or add a comment. |
| attach_fileA | Attach a file to a Jira ticket. Provide the issue key and absolute file path. |
| link_ticketsA | Link two Jira tickets together. Default relationship is 'relates to'. Common types: 'relates to', 'Blocks', 'Duplicate', 'Cloners'. |
| get_confluence_pageA | Fetch a Confluence page by numeric ID or full URL. Returns title, space, version, and body as plain text. |
| search_confluenceB | Search Confluence pages using CQL. Example: 'space = SECENG AND type = page' |
| get_space_pagesC | List pages in a Confluence space. Example: space_key='SECENG' |
| create_confluence_pageC | Create a new Confluence page in a space. Optionally specify a parent page ID. |
| update_confluence_pageC | Update an existing Confluence page's content. |
| move_confluence_pageA | Move a Confluence page under a new parent page. Provide the page ID and the target parent page ID. |
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 20 tools
Each tool targets a distinct resource and action within Confluence, Bitbucket, or Jira. No two tools have overlapping functionality, and the descriptions clearly differentiate their purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_space_pages, create_ticket, list_bitbucket_repos). No mixing of conventions or unclear verbs.
20 tools cover three distinct Atlassian products, which justifies a higher count. While slightly above the ideal 3-15 range, the scope is well-defined and each tool serves a clear purpose.
The tool set covers core CRUD operations for Jira, Confluence, and Bitbucket, along with search and linking. Minor gaps exist, such as missing delete operations and no Bitbucket repo/PR creation, but the most common workflows are supported.