MCP servers that can create a branch
5 verified servers expose a tool that can create a branch
Branch is one word for two related moves: a git branch for an isolated line of code, and a database branch for an isolated copy of your data. Both let an agent work on a change without touching the main line, and several servers expose the create as a single call.
These verified servers let an agent create a branch, in a repository or a database.
Git
Anthropic (Model Context Protocol)
Reference MCP server for local Git: status, diffs, commits, branches, and history on a repo path.
git_create_branch
git_create_branch cuts a new branch from an optional base in a local repository, the plain-git version for an agent working in a checkout.
GitHub
GitHub
GitHub's official remote MCP server for repos, issues, pull requests, Actions, and code search.
create_branch
On GitHub, create_branch opens a new branch in a repository, the starting point before an agent commits and raises a pull request.
Neon
Neon
Neon's official MCP server lets agents create projects and branches, run SQL, and drive safe schema migrations on serverless Postgres.
create_branch
Neon goes further than code: create_branch branches the database itself, so an agent gets an isolated Postgres to run a migration against and drop afterward.
Supabase
Supabase (community)
Connects agents to a Supabase project: run SQL, inspect schema, read logs, and manage edge functions.
create_branch
Supabase's create_branch spins up a development branch with migrations carried from production, an isolated copy to test schema changes before they ship.
Gitea
Gitea
Gitea's official MCP server for repos, branches, issues, pull request reviews, releases, Actions, and wikis on any Gitea instance.
create_branch
Self-hosted forges get the same isolation: create_branch opens a branch in a Gitea repository you run in-house.
What to know
The code side is familiar: git, GitHub, and Gitea cut a new branch from a base so an agent can commit work in isolation before opening a PR. The database side is the interesting one. Supabase and Neon branch the database itself, schema and data, which gives an agent a real environment to run a migration or a risky query against and then discard. That is the safe way to let a model touch a database: not on production, but on a branch it can throw away.
Branches are cheap to make and easy to forget, which is the catch. An agent that branches per task and loses track of what it created leaves a trail of stale branches behind. Which branch belongs to which piece of work is context worth keeping, so cleanup stays possible later.
Questions
- A database branch is different from a git branch, right?
- Yes. A git branch (git, GitHub, Gitea here) isolates a line of code. A database branch (Neon, Supabase) isolates a copy of the database, schema and data, so an agent can run a migration or a risky query against it without touching production. Same word, two different units of isolation.
- Why give an agent a database branch?
- Because it is the safe way to let a model touch a database. Instead of running a migration or a destructive query against production, the agent runs it on a throwaway branch, checks the result, and discards it. Neon and Supabase make that branch a single tool call.