bitbucket-mcp-server
by fnops
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP server bind address | 0.0.0.0 |
| MCP_PORT | No | HTTP server port (only when MCP_TRANSPORT=http) | 3000 |
| NODE_ENV | No | Environment: development, production, test | production |
| LOG_LEVEL | No | Log level: fatal, error, warn, info, debug, trace | info |
| MCP_TRANSPORT | No | Transport type: stdio (local) or http (remote) | stdio |
| BITBUCKET_API_URL | No | API base URL (override for testing) | https://api.bitbucket.org/2.0 |
| BITBUCKET_USERNAME | No | Bitbucket account email (Basic auth, legacy). Required if BITBUCKET_API_TOKEN is not set. | |
| BITBUCKET_API_TOKEN | No | API token (Bearer auth, recommended). If provided, takes priority over username/password. | |
| BITBUCKET_WORKSPACE | Yes | Workspace slug | |
| BITBUCKET_APP_PASSWORD | No | App password (Basic auth, legacy). Required if BITBUCKET_API_TOKEN is not set. |
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/fnops/bitbucket-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server