db3-atlassian-mcp
by db3net
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'. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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
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/db3net/db3-atlassian-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server