The `bbmd` cli should be the superior to MCP when used by AI agents.
Atlacp MCP server exists for a simple reason — assistants are far more useful when they can act on Atlacp directly instead of describing what you should do. The bbmd cli should be the superior to MCP when used by AI agents.
Once Atlacp is connected, these are the calls the assistant has available:
bitbucket_add_pr_comment — add a comment to a pull requestbitbucket_approve_pr — approve a pull requestbitbucket_create_pr — create a pull requestbitbucket_create_pr_task — create a task on a pull requestbitbucket_get_file_content — get file content from a repository at a specific commitbitbucket_get_pr_diff — get the diff of a pull requestbitbucket_get_pr_diffstat — get the diffstat of a pull requestbitbucket_list_pr_comments — list pull request commentsbitbucket_list_pr_tasks — list tasks on a pull requestbitbucket_merge_pr — merge a pull requestbitbucket_read_pr — read a pull requestbitbucket_resolve_pr_comment — resolve a pull request comment threadSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Atlacp's toolset — bitbucket_add_pr_comment, bitbucket_approve_pr, bitbucket_create_pr and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gemyago; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| bitbucket_add_pr_comment | add a comment to a pull request. |
| bitbucket_approve_pr | approve a pull request. |
| bitbucket_create_pr | create a pull request. |
| bitbucket_create_pr_task | create a task on a pull request. |
| bitbucket_get_file_content | get file content from a repository at a specific commit. |
| bitbucket_get_pr_diff | get the diff of a pull request. |
| bitbucket_get_pr_diffstat | get the diffstat of a pull request. |
| bitbucket_list_pr_comments | list pull request comments. |
| bitbucket_list_pr_tasks | list tasks on a pull request. |
| bitbucket_merge_pr | merge a pull request. |
| bitbucket_read_pr | read a pull request. |
| bitbucket_resolve_pr_comment | resolve a pull request comment thread. |
| bitbucket_request_pr_changes | request changes on a pull request. |
| bitbucket_update_pr | update a pull request. |
Or if you prefer HTTP transport:
```json
{
"mcpServers": {
"Bitbucket": {
"url": "http://localhost:8080"
}
}
}Configuration as documented by the project. Restart the client after saving.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.