Model Context Protocol

MCP for version control, hosted and OAuth-secured.

Branchive ships a hosted MCP server so AI agents — Claude Code, Claude Desktop, Cursor, or any other MCP client — can work directly on your repos: browse code, open pull requests, and commit changes, all scoped to the exact permissions your account already has.

Get connected

Three ways to connect.

Pick your client. Each one talks to the same hosted server at https://app.branchive.io/mcp.

Claude Desktop & claude.ai

Settings → Connectors → Add custom connector → paste the URL below → sign in with your Branchive account.

https://app.branchive.io/mcp

Claude Code

Add the remote server with the CLI — it opens the OAuth sign-in in your browser the first time you use it.

claude mcp add --transport http branchive https://app.branchive.io/mcp

Cursor & other MCP clients

Most MCP-compatible clients accept a raw server config. Drop this into your client's MCP settings JSON.

{
  "mcpServers": {
    "branchive": {
      "type": "http",
      "url": "https://app.branchive.io/mcp"
    }
  }
}

Every client authenticates the same way — a real OAuth 2.1 sign-in against your Branchive account, not a static API key. An agent can only see and touch the repos your account already has access to.

Scoped to your account

What agents can do.

Every call runs under the OAuth grant you approved for that session — an agent can't see or reach anything your account can't.

Read access

✓ Browse repos, file trees, and branches

✓ Read file contents, diffs, and commit history

✓ Search code across a repo

✓ List pull requests, issues, releases, wiki pages, and active locks

With write access

✓ Commit changes to a branch

✓ Open, comment on, approve, and merge pull requests

✓ Create and update issues and releases

✓ Acquire and release file locks

✓ Create and edit wiki pages

With admin access

✓ Add or remove collaborators and set their roles

✓ Manage labels and required-review policy

✓ Create webhooks to wire pushes and reviews into your CI

✓ Edit repo settings, visibility, and deletion

Each action needs the matching permission on that specific repo — read, write, or admin — the same rule the web app and desktop client already enforce, and every request is capped to the scope you approved at sign-in. It's the full toolset the Branchive UI exposes, driven by your agent.

Hosted, not local

A server you don't have to run.

Branchive's MCP server is hosted — there's no local process to install, keep updated, or leave running on your machine. It's OAuth-secured and scoped to your exact per-repo permissions, so an agent's session is exactly as powerful as you are, and no more. loregui's MCP server is local-only, GitHub's remote server is in public preview, and Perforce's community-maintained MCP server isn't officially supported by Perforce. See the full, feature-by-feature breakdown on the comparison page.

Give your agent a seat at the table.

Download Branchive Desktop Sign in with Google

Home · Pricing · Compare