What is the key difference between Tod and Bbkt?

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

How do I install Tod or Bbkt 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 Tod and Bbkt free or paid?

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

Which MCP server has more tools and community activity?

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

Can I use both Tod and Bbkt 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

Tod vs Bbkt

In-depth architectural comparison of the Tod and Bbkt 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

Tod

Version Control · Local stdio

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

Bbkt

Version Control · Local stdio

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

Verdict Summary: Choose Tod if you need specialized Version Control tools running via a local process. Choose Bbkt 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 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.
Primary tools included: Run CI/CD jobs against local changes, branches, or tags, Stream CI job logs in real time, Check out issues and pull requests with submodule handling.

Explore Tod Details

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.

Feature & Specification Comparison

Specification	Tod theonedev Version Control	Bbkt zach-snell Version Control
Summary	A MCP server for OneDev for CI/CD pipeline editing, issue workflow automation, and pull request review	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.
Category & Scope	Version Control

Tools & Capabilities Breakdown

Tod Tools (6)

Run CI/CD jobs against local changes, branches, or tags

Stream CI job logs in real time

Check out issues and pull requests with submodule handling

Query and edit OneDev issues, pull requests, and builds

Inspect build logs, changes, and code problem reports

Validate and migrate OneDev build specifications

Bbkt Tools (9)

manage_workspaces

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).

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"
      }
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Tod More alternatives to Bbkt Version Control category hub