bb-mcp-server

# Unified Tool Server This directory contains an alternative Bitbucket MCP server implementation that exposes all functionality through a **single unified tool** backed by comprehensive server instructions, following the patterns outlined in the [MCP Server Instructions blog post](https://blog.modelcontextprotocol.io/posts/2025-11-03-using-server-instructions/). ## Overview Instead of providing 13 separate tools (`pr_list`, `pr_overview`, `pr_review`, etc.), the unified server exposes a single `bitbucket_operation` tool with an `action` parameter. The server instructions (~200 lines) provide: - **Recommended workflows** for common tasks (PR review, creation, pipeline debugging, workspace discovery) - **Action-specific guidance** with parameter requirements and usage patterns - **Performance optimization** tips (batching, pagination, auto-reviewers) - **Rate limits and constraints** to prevent API abuse - **Error handling** guidance for common issues - **Security notes** for credential management ## Architecture ``` server.py # Main entry point ├─ src/modules/tools/unified.py # Single tool implementation └─ Uses same infrastructure as tools_server.py: ├─ src/modules/resources/ # MCP resources (unchanged) ├─ src/modules/prompts/ # MCP prompts (unchanged) ├─ src/modules/middleware/ # Auth middleware (unchanged) └─ src/utils/ # Shared utilities (unchanged) ``` ## Running the Unified Server ```bash # Stdio (default) -- for Claude Desktop and other MCP clients. # --host/--port are ignored unless --transport http is also passed. python server.py # HTTP -- --transport http is REQUIRED; without it the server starts in stdio # and silently ignores --host/--port. python server.py --transport http --host 0.0.0.0 --port 8000 # With environment variables (still needs --transport http; the env vars set the # bind address, they do not select the transport) FASTMCP_HOST=localhost FASTM…