What is the key difference between Bbkt and Tod?

Bbkt belongs to the Version Control category with local stdio execution, while Tod belongs to the Version Control category with local stdio execution.

How do I install Bbkt or Tod in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Bbkt and Tod free or paid?

Bbkt operates under a Free / Open Source model (API Key required). Tod operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Bbkt lists 9 tools with 1 views and 4 GitHub stars. Tod lists 6 tools with 4 views and 14 GitHub stars.

Can I use both Bbkt and Tod together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Bbkt vs Tod

In-depth architectural comparison of the Bbkt and Tod MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Bbkt

Version Control · Local stdio

Quality: 49/100 (Fair) | Auth: API Key required

Tod

Version Control · Local stdio

Quality: 40/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Bbkt if you need specialized Version Control tools running via a local process. Choose Tod if your workspace requires Version Control integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Bbkt when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: BITBUCKET_USERNAME, BITBUCKET_API_TOKEN, BITBUCKET_ACCESS_TOKEN, BITBUCKET_OAUTH_CLIENT_ID, BITBUCKET_OAUTH_CLIENT_SECRET, BBKT_OAUTH_CALLBACK_PORT, BBKT_PROFILE.
Primary tools included: manage_workspaces, manage_repositories, manage_refs.

Explore Bbkt Details

Choose Tod when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ONEDEV_SERVER_URL, ONEDEV_ACCESS_TOKEN, ONEDEV_TRUST_CERTS_FILE.

Feature & Specification Comparison

Specification	Bbkt zach-snell Version Control	Tod theonedev Version Control
Summary	Bitbucket Cloud CLI and MCP server. Manages workspaces, repos, PRs, pipelines, issues, and source code. Token introspection hides tools the API key can't use.	A MCP server for OneDev for CI/CD pipeline editing, issue workflow automation, and pull request review
Category & Scope	Version Control

Tools & Capabilities Breakdown

Bbkt Tools (9)

manage_workspaces

—

manage_repositories

repository

manage_refs

repository

manage_commits

repository

manage_source

repository

manage_pull_requests

pullrequest

manage_pr_comments

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Bbkt Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "zach-snell-bbkt": {
      "command": "npx",
      "args": [
        "-y",
        "zach-snell-bbkt"
      ],
      "env": {
        "BITBUCKET_USERNAME": "YOUR_BITBUCKET_USERNAME_HERE",
        "BITBUCKET_API_TOKEN": "YOUR_BITBUCKET_API_TOKEN_HERE",
        "BITBUCKET_ACCESS_TOKEN": "YOUR_BITBUCKET_ACCESS_TOKEN_HERE",
        "BITBUCKET_OAUTH_CLIENT_ID": "YOUR_BITBUCKET_OAUTH_CLIENT_ID_HERE",
        "BITBUCKET_OAUTH_CLIENT_SECRET": "YOUR_BITBUCKET_OAUTH_CLIENT_SECRET_HERE",
        "BBKT_OAUTH_CALLBACK_PORT": "YOUR_BBKT_OAUTH_CALLBACK_PORT_HERE",
        "BBKT_PROFILE": "YOUR_BBKT_PROFILE_HERE"
      }
    }
  }
}

Tod Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "theonedev-tod": {
      "command": "npx",
      "args": [
        "-y",
        "theonedev-tod"
      ],
      "env": {
        "ONEDEV_SERVER_URL": "YOUR_ONEDEV_SERVER_URL_HERE",
        "ONEDEV_ACCESS_TOKEN": "YOUR_ONEDEV_ACCESS_TOKEN_HERE",
        "ONEDEV_TRUST_CERTS_FILE": "YOUR_ONEDEV_TRUST_CERTS_FILE_HERE"
      }
    }
  }
}

Frequently Asked Questions

Bbkt is categorized under Version Control and uses a local stdio subprocess. In contrast, Tod belongs to Version Control using local stdio subprocess. Select Bbkt when you need capabilities focused on version control and Tod when you require tools for version control.

More alternatives to Bbkt More alternatives to Tod Version Control category hub Canonical compare URL

Bbkt vs Tod

At a Glance & Executive Verdict

Which MCP Server Should You Choose?

Choose Bbkt when:

Choose Tod when:

Feature & Specification Comparison

Tools & Capabilities Breakdown

Bbkt Tools (9)

Ready-to-Paste Client Configurations

Frequently Asked Questions

Related MCP Server Comparisons

Popular comparisons with Bbkt

Popular comparisons with Tod

Tod Tools (6)