rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Git and forge ops: local git via gitoxide, plus GitHub, GitLab, Gitea and Forgejo
Skills, die der KI diese Art Arbeit beibringen; sie funktionieren zusammen mit diesem
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Listen sind nach einem Nutzungswert (von 100) aus diesen Teilen sortiert
| Beliebtheit | 17/80 | GitHub-Sterne oder wöchentliche Downloads: der größere Wert zählt 60, der kleinere 20 |
|---|---|---|
| Aktualität | 12/12 | Volle Punkte für Release oder Codeänderung in 30 Tagen |
| Antwortet noch | 0/8 | Der Cloud-Endpoint antwortete bei der letzten Prüfung |
| Nutzungswert | 29/100 |
Qualität: 3/3 Basisprüfungen bestanden (angezeigt, nicht zur Sortierung) · Schwung: Noch keine Daten (Nur im Tab Im Trend verwendet)
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
3/3 Prüfungen bestanden · Läuft auf deinem Computer
Zuerst: Welche KI nutzt du?
Wähle deine App, dann erscheinen die Schritte unten.
Claude kann Skipper noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
ChatGPT kann Skipper noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
B · Andere in Entwicklertools, die mit ChatGPT funktionieren
Aus den meistgenutzten derselben Kategorie, nur solche, die per Adresse ohne Schlüssel verbinden
Claude Code kann Skipper noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
Cursor kann Skipper noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
VS Code kann Skipper noch nicht verbinden
Der Anbieter hat noch keine Installationsangaben im MCP-Verzeichnis
cargo: skipperBasierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.
Laufen auf deinem Computer in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 19. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto seuros bestätigt, dem das Repo gehört
Code zuletzt geändert: vorgestern
Nutzt BSD-2-Clause
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Nicht geprüft: nur npm- und PyPI-Pakete mit Version lassen sich prüfen
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/servers/seuros-skipper)Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.
Noch keine Bewertungen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt vorgestern geändert, und die neueste Version (0.10.3) kam vor 10 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Rust auf deinem Computer.
In derselben Kategorie: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| Dieser Skipper | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Läuft wo | Wird auf deinem Rechner installiert | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | In der Cloud oder auf deinem Rechner |
| Braucht Schlüssel | Nein | Nein | Nein | Nein | Nein | Nein |
| Mit + in Claude hinzufügen | Nein | Nein | Nein | Ja | Nein | Nein |
| Basisprüfungen | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| Lizenz | BSD-2-Clause | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Preis | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register |
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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 20, and shows fewer than that: only the ones this repository can actually use, and the four that write only when you turn them on.
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.
By default, no skipper tool can write to a forge. There is no create, delete, close, or fork, and out of the box no merge, push, fetch, or pull either: the only state any tool changes is local (staging, committing, local branches), so an agent cannot move a commit to a remote through skipper.
Merging and syncing are opt-in, in your global config only (~/.config/skipper/config.toml); a repository's own skipper.toml cannot turn them on:
[writes]
enabled = true # show pr_merge, git_push, git_pull, git_fetch confirm = true # default: ask before each merge or push
With confirm, every merge and push is put to you through the client (MCP elicitation) with exactly what will happen, such as push master to github, origin or rebase #6 "chore: release 0.6.0" (release → master), and runs only if you approve. A client that cannot ask is refused; confirm = false lets writes run unattended. Even then nothing forces or deletes: +ref, a:b and -option refspecs are refused, and a merge is pinned to the head sha it was checked at, so a push in between fails it.
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 | REST and GraphQL over rama, token from gh auth token |
| GitLab | the glab CLI |
| 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.
For forges, skipper reuses the credentials the CLIs already hold. It stores no tokens of its own. Log in as usual:
gh auth login
glab auth login tea login add
For GitHub, skipper asks gh auth token for the token once per host (it honours GH_TOKEN), keeps it in memory only, and calls the API itself: one HTTP request instead of a gh process per query. A 401 fetches the token again, so gh auth refresh or a rotated token needs no restart.
For Gitea and Forgejo, skipper reads the token from tea's config instead of running tea, which can block on an interactive prompt that never resolves under a non-interactive server. tea login add is still how you set it up.
Building from source requires Rust 1.99 or newer. The repository pins Rust 1.99.0 for local and release builds.
| Provider | CLI | Minimum | Auth |
|---|---|---|---|
| GitHub | gh | 2.50 | gh auth login |
| GitLab | glab | 1.40 | glab auth login |
| Gitea / Forgejo | tea | 0.9 | tea login add |
Local git needs no binary: it runs in-process on gitoxide.
A missing, outdated, or unauthenticated CLI just hides that provider's tools. An auth check that fails on the network (timeout, connection reset) is not treated as logged out: skipper retries it with backoff for a few minutes and announces the tools with tools/list_changed once it answers. Detection results are logged to stderr, which MCP clients keep in their server logs.
Tools follow the repository, not the toolbox. A forge's tools appear only when all of the following hold:
Git tools need only a repository; they do not depend on any CLI.
So an installed gh does not put GitHub tools in front of a checkout hosted on Forgejo. github.com, gitlab.com, and codeberg.org are recognized out of the box; self-hosted instances are mapped in config:
# ~/.config/skipper/config.toml (global) or ./skipper.toml (per repo)
[hosts] "github.enterprise.com" = "github" "gitlab.internal" = "gitlab" "192.168.3.20" = "forgejo"
Forge names accept aliases: github/gh, gitlab/glab, and gitea/forgejo/tea (Gitea and Forgejo are both driven by tea). Remotes whose host isn't mapped simply expose no forge tools. The unmapped hosts are logged at startup so you know what to add.
Visibility is re-evaluated while the server runs. The remotes are re-read before every tools/list and tools/call, so git init, git remote add, re-pointing a remote, or removing one applies to the next call; a background watcher also emits notifications/tools/list_changed within a few seconds so clients re-list. No restart needed.
curl -fsSL https://raw.githubusercontent.com/seuros/skipper/master/scripts/install.sh | bash
It picks the latest release and the right build for your machine, and installs to ~/.local/bin. Pass --prefix for somewhere else or --version for a specific tag. Prebuilt for Linux and macOS, x86_64 and arm64.
Or build it yourself:
cargo install skipper
Either way you get the skipper binary. Skipper is a server, not a library: the crate builds the binary alone. Depend on the MCP tools and resources.
Skipper speaks MCP over stdio. Add it to your client config:
{
"mcpServers": { "skipper": { "command": "skipper" } } }
| Tool | Provider | Purpose |
|---|---|---|
repo_search | Gitea/Forgejo | Search repositories by name, paginated |
gh_repo_list | GitHub | List repositories for the authenticated user |
glab_project_list | GitLab | List projects for the authenticated user |
build_status | GitHub/GitLab | CI run or pipeline status for the current repository |
build_watch | GitHub/GitLab | Wait for a CI run's status to change, up to a bounded time; commit= waits for every run of a commit (task-capable) |
pr_build_wait | GitHub | Wait for a PR's checks to finish; structured verdict (task-capable) |
pr_watch | GitHub | Watch PRs for merge, close, comments, reviews, checks, and pushes (task-capable) |
pr_merge | GitHub, writes | Merge a PR after checking state, draft, conflicts, checks and the allowed method; confirmed |
git_push | writes | Push branches and tags to one, several, or all remotes; never forces; confirmed |
git_pull | writes | Fast-forward the branch to its upstream; never merges |
git_fetch | writes | Fetch one or all remotes, pruning deleted branches |
git_status | git | Staged, unstaged, and untracked files |
git_diff | git | Scoped patches, stats, or changed paths |
git_log | git | Recent commits |
git_show | git | Commit details with subject, body, trailers |
git_show_file | git | A tracked file at a revision |
git_blame | git | Per-line attribution |
git_add | git | Stage explicit paths |
git_commit | git | Commit staged changes, with trailers or amend |
git_branch | git | Create or delete a local branch |
Questions about *this* repository are resources, not tools, and they are scoped by the workspace's remotes rather than your account.
| URI | Provider | Contents |
|---|---|---|
skipper://workspace | any | The current workspace: working directory, repo root, branch, HEAD, dirty state, remotes (credentials stripped) and the forge each maps to, the current remote marked |
skipper://repo | Gitea/Forgejo | The repository this workspace's remote points at, trying the current remote, then origin, when several match |
skipper://issues/{state} | GitHub, Gitea/Forgejo | The current remote's last 30 issues in open, closed or all state, latest update first: number, title, state, author, labels, comment count, created and updated times |
skipper://issue/{number} | GitHub, Gitea/Forgejo | One issue of the current remote: title, state, author, creation time, labels, assignees, the full body and every comment, cleaned like PR comments |
skipper://pr/{number} | GitHub | What a merge decision needs, in one read: state, draft, head/base and head sha, mergeability, review decision, the checks' verdict (conclusion, counts, failed checks), allowed and default merge methods, labels, size; current selects the current branch's |
skipper://pr/{number}/files | GitHub | The files a PR changes, with added and deleted lines |
skipper://pr/{number}/checks | GitHub | Check matrix for a PR, by workflow; links and descriptions on failures only; current selects the current branch's |
skipper://pr/{number}/comments | GitHub | A PR's state (open/closed/merged), its description, and every inline review comment, conversation comment and review, in full: HTML comments and tags dropped, entities decoded, collapsed opened, and bot machinery removed (CodeRabbit's tool transcripts, run info, buttons, share links; release-please's greeting and footer) |
skipper://pr/{number}/comments/{kind} | GitHub | The same, keeping only inline, comment or review notes (all keeps every one) |
skipper://watch/comments/{kind} | GitHub | skipper://pr/{number}/comments/{kind} for every PR under pr_watch, in one read; recently finished PRs report their final state, and a PR that cannot be read reports its error |
skipper://prs/{state}/{author} | GitHub | The last 30 PRs in open, closed, merged or all state by an author (me for the authenticated user): number, state, merge time |
skipper://watch | GitHub | PRs under pr_watch: status, checks, recent and undelivered events |
Percent-encode author names in PR-list URIs. Bot brackets must be %5B and %5D, for example: skipper://prs/open/github-actions%5Bbot%5D?repo=seuros/behavior_machines. The GitHub search still receives the login github-actions[bot].
Issue resources read from one remote, picked fresh on every read:
branch. .remote);origin.With several remotes and none of these, the read fails and says so rather than guess. Switching branches or running git branch -u moves the next read to the other forge; no restart. Every issue payload names the forge and repo it came from. A Gitea/Forgejo token needs the read:issue scope.
GitHub-only reads (PR checks and discussion, CI runs, pr_watch) take the current remote when it is on GitHub, else the one GitHub repo among the remotes, so they keep working while the branch tracks a mirror on another forge. Two different GitHub repos (a fork and its upstream) with neither current is an error naming both.
Any PR or issue read can name another repo: ?repo= on the resources (skipper://pr/7289/comments?repo=upstream, skipper://issues/open?repo=matz/spinel) and repo on pr_watch, pr_merge and pr_build_wait, as a remote name or owner/name. Skipper never follows GitHub's fork link on its own: it is history, not intent (trailblazer/representable is a fork of roxml). A PR missing from a fork says what the parent is, and the agent picks. A branch's PR read on another repo is still the one from this checkout's branch. Ever