MCP server for git repositories: local git in-process via gitoxide, plus GitHub, GitLab, Gitea and Forgejo through their CLIs
MCP server for working in a git repository: local git in-process, and GitHub, GitLab, Gitea, and Forgejo behind one small set of tools.
The existing forge MCP servers expose the API, not a workflow. Counted from their own sources: GitHub's has ~125 tools, GitLab's ~88, Gitea's ~54. One tool per endpoint, three servers, three vocabularies, and an agent that has to work out which one it is talking to.
Skipper registers 15, and shows fewer than that: only the ones this repository can actually use.
An agent does not need to be emperor of your forge. It does not need to create or destroy an organization on any given turn. It needs to know what this repository is, whether the build passed, and what broke. Skipper exposes that and skips the rest.
No skipper tool can write to a forge. There is no create, delete, merge, close, or fork. The only state any tool changes is local: staging, committing, and local branches. There is no push, fetch, or pull, so an agent cannot move a commit to a remote through skipper at all.
The destructive operations still exist in the CLIs. To delete a release, an agent calls gh directly, which your harness can allow or deny with one rule. That is one binary to gate instead of 267 tools to audit.
Layer Transport ------------------ local git gitoxide, in-process GitHub, GitLab the gh and glab CLIs Gitea, Forgejo REST over rama, token from tea's config
Local git needs no credentials: it reads and writes the repository directly, never the network.
From the project README.
Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:
[](https://mcp.liqiwa.com/s/seuros--skipper.html)
Desktop automation MCP server — computer use for any AI agent: control screen, windows, mouse/keyboard, and Chrome via Model Context Protocol (stdio)
naw103/foremergeCatch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
nettanvirdev/inertiainertia-ai: a desktop workspace for AI agents. Chat, built-in tools, MCP and OpenAPI integrations, Docker/Daytona sandboxes with a live desktop, routines and memory. Bring your own model and keys.
NotNull92/workforge-mcpWorkForge is a Windows MCP gateway that lets ChatGPT inspect files, resume Git work, make SHA-guarded edits, read images, and run supervised PowerShell jobs.
BANG404/openagentA modern, multi-agent desktop AI client built with Tauri, SvelteKit, and Rust.
omaekumiko2-create/kruLocal-first MCP password and credential manager for AI agents. Use passwords, API keys, SSH identities, and TOTP without exposing hidden plaintext to the model.
The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.