原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Skipper

作者:seuros版本 0.10.3i★ 23i在你的电脑上运行代码仓库 ↗
注册名称io.github.seuros/skipper

安装方法

What it does

Git and forge ops: local git via gitoxide, plus GitHub, GitLab, Gitea and Forgejo

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 开发者工具

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

作者:morluto★ 467,2351 个 skill

Skill · 操作手册

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

作者:multica-ai★ 234,1251 个 skill

Skill · 操作手册未注明许可证

graphify

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.

作者:Graphify-Labs★ 149,8731 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度17/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分29/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Skipper

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Skipper

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 开发者工具 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Skipper

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Skipper

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Skipper

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Skipper 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
BSD-2-Clause
连接方式
在你的电脑上运行
最新版本i
0.10.3
发布到注册中心i
2026年11月9日
代码最后更新i
2026年11月17日
作者
seuros
软件包
cargo: skipper
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 seuros 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于前天

  • ✓ 通过

    有许可证

    使用 BSD-2-Clause

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/seuros-skipper.svg)](https://mcp.popnx.com/en/servers/seuros-skipper)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 6136 个服务器的 93%
  • 发布到注册中心的时间比此分类中其他 6136 个服务器的 80% 更新
  • 基础检查结果等于或优于此分类中其他 6136 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Skipper 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于前天,最新版本(0.10.3)于10天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Rust。

有什么可以替代它?

同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

作者:ahmedkhaleel2004广泛使用★ 1.9万2个月前更新

在云端运行✓ 服务方 · gitdiagram.comPopNx 团队已实际试用

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

作者:Appllama广泛使用★ 52303个月前更新

在云端运行✓ 服务方 · appllama.io

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

作者:omnara-ai广泛使用★ 34172个月前更新

在云端运行✓ 服务方 · omnara.com

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

作者:repowise-dev广泛使用↓ 6506/周★ 8180 整个仓库的星标6天前更新

电脑或云端✓ 服务方 · repowise.dev
与相似项目对比
本项
Skipper
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查3/34/44/44/44/45/5
许可证BSD-2-ClauseMITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

skipper

MCP server for working in a git repository: local git in-process, and GitHub, GitLab, Gitea, and Forgejo behind one small set of tools.

Why

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.

How it talks to things

LayerTransport
local gitgitoxide, in-process
GitHubREST and GraphQL over rama, token from gh auth token
GitLabthe glab CLI
Gitea, ForgejoREST over rama, token from tea's config

Authentication

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.

Requirements

Building from source requires Rust 1.99 or newer. The repository pins Rust 1.99.0 for local and release builds.

ProviderCLIMinimumAuth
GitHubgh2.50gh auth login
GitLabglab1.40glab auth login
Gitea / Forgejotea0.9tea 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.

Tool visibility

Tools follow the repository, not the toolbox. A forge's tools appear only when all of the following hold:

  1. the workspace is a git repository,
  2. one of its remotes points at that forge, and
  3. the forge's CLI is installed, new enough, and authenticated.

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.

Installation

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.

MCP setup

Skipper speaks MCP over stdio. Add it to your client config:

{

"mcpServers": { "skipper": { "command": "skipper" } } }

Tools

ToolProviderPurpose
repo_searchGitea/ForgejoSearch repositories by name, paginated
gh_repo_listGitHubList repositories for the authenticated user
glab_project_listGitLabList projects for the authenticated user
build_statusGitHub/GitLabCI run or pipeline status for the current repository
build_watchGitHub/GitLabWait 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_waitGitHubWait for a PR's checks to finish; structured verdict (task-capable)
pr_watchGitHubWatch PRs for merge, close, comments, reviews, checks, and pushes (task-capable)
pr_mergeGitHub, writesMerge a PR after checking state, draft, conflicts, checks and the allowed method; confirmed
git_pushwritesPush branches and tags to one, several, or all remotes; never forces; confirmed
git_pullwritesFast-forward the branch to its upstream; never merges
git_fetchwritesFetch one or all remotes, pruning deleted branches
git_statusgitStaged, unstaged, and untracked files
git_diffgitScoped patches, stats, or changed paths
git_loggitRecent commits
git_showgitCommit details with subject, body, trailers
git_show_filegitA tracked file at a revision
git_blamegitPer-line attribution
git_addgitStage explicit paths
git_commitgitCommit staged changes, with trailers or amend
git_branchgitCreate or delete a local branch

Resources

Questions about *this* repository are resources, not tools, and they are scoped by the workspace's remotes rather than your account.

URIProviderContents
skipper://workspaceanyThe current workspace: working directory, repo root, branch, HEAD, dirty state, remotes (credentials stripped) and the forge each maps to, the current remote marked
skipper://repoGitea/ForgejoThe repository this workspace's remote points at, trying the current remote, then origin, when several match
skipper://issues/{state}GitHub, Gitea/ForgejoThe 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/ForgejoOne 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}GitHubWhat 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}/filesGitHubThe files a PR changes, with added and deleted lines
skipper://pr/{number}/checksGitHubCheck matrix for a PR, by workflow; links and descriptions on failures only; current selects the current branch's
skipper://pr/{number}/commentsGitHubA 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}GitHubThe same, keeping only inline, comment or review notes (all keeps every one)
skipper://watch/comments/{kind}GitHubskipper://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}GitHubThe last 30 PRs in open, closed, merged or all state by an author (me for the authenticated user): number, state, merge time
skipper://watchGitHubPRs 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].

Current remote

Issue resources read from one remote, picked fresh on every read:

  1. the remote the checked-out branch tracks (branch. .remote);
  2. else the only remote;
  3. else 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

只显示了开头部分;其余内容请在仓库中阅读