What it does
Git on Nostr via gittr.space: repos, push, issues, PRs, stars, bounties. Nostr identity (NIP-34).
- Connects –
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
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.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 16/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
ChatGPT 暂时无法连接 gittr-mcp
开发者尚未在 MCP 注册表中填写安装方式
你可以改用这些方式
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 gittr-mcp
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 gittr-mcp
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 gittr-mcp
开发者尚未在 MCP 注册表中填写安装方式
一览
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 arbadacarbaYK 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于4天前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/arbadacarbayk-gittr-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6136 个服务器的 69%
- 发布到注册中心的时间比此分类中其他 6136 个服务器的 19% 更新
- 基础检查结果等于或优于此分类中其他 6136 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
gittr-mcp 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于4天前,最新版本(1.0.2)于4个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 gittr-mcp | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
gittr-mcp
Let your AI agent (or app) use [gittr](https://gittr.space) — Nostr git hosting — like a developer would — create repos, push code, open and merge pull requests, manage issues, and work with Lightning bounties — using your Nostr identity, not a GitHub login.
Works with Cursor, Claude Desktop, VS Code / Copilot MCP, Windsurf, OpenClaw, or any host that speaks the Model Context Protocol over stdio.
Needs Node 22.23.4, 24.22.1, or 26.12.1 (or a newer build on those lines). Node 18 and 20 have no fix for the October 2026 certificate and Brotli bugs, and gittr-mcp exits instead of starting on those.
Docs hub: gittr-docu — product map and how this MCP sits next to the website.
This repo’s Page: root index.html. After Push Manifest, save site name gittr-mcp.
Why use this?
| Without gittr-mcp | With gittr-mcp |
|---|---|
| You copy-paste between chat and the gittr website | The agent calls tools: push files, publish repo metadata, open issues/PRs |
| Custom scripts for NIP-98 bridge auth and NIP-34 signing | Signing, challenge handling, and relay checks are built in |
| Unclear whether a push “really” landed on Nostr | Tools return pass/fail plus verification / nextSteps for automation |
End result: one MCP server connects your agent to decentralized git on Nostr — same account as on gittr.space (nsec / keys file), no separate vendor account for the agent.
Hosting note: The website Create/Import flow stays browser-local until announce/Push. MCP createRepo / mirrorRepo / pushToBridge write the git the same way the website does. The clone addresses are the servers saved under Settings → Relays (yours first), then the public copies. Soft-delete POSTs the tombstone to the bridge so disk is wiped.
Where this sits (platform map)
gittr-mcp is the agent door into the same platform humans use in the browser. You are here = gittr-mcp (this repo, teal). Cyan-outlined host boxes = public hostnames (git. / pages. / relay.gittr.space) (teal = this repo; cyan outline = host URLs).
flowchart TB
Agent["AI host Cursor / Claude / …"] MCP["★ YOU ARE HERE · gittr-mcp this repo · agent tools"] UI["gittr Client gittr.space"] Bridge["gitnostr Bridge git.gittr.space SSH / HTTPS git"] RelayGittr["gittr Pyramid relay relay.gittr.space wss · open forge + GRASP"] Relays["Other Nostr relays"] Pages["Pages / nsite pages.gittr.space"] Remote["git remote nostr optional"]
Agent -->|MCP tools| MCP MCP -->|HTTPS + Nostr auth| Bridge MCP -->|sign NIP-34 events| RelayGittr MCP -->|sign NIP-34 events| Relays UI --> RelayGittr UI --> Relays UI --> Bridge Pages --> Relays Remote -.-> Relays
classDef youAreHere fill:#0f766e,stroke:#5eead4,stroke-width:3px,color:#ecfdf5 classDef hostUrl fill:#164e63,stroke:#22d3ee,stroke-width:2px,color:#ecfeff class MCP youAreHere class Bridge,Pages,RelayGittr hostUrl
| Piece | Host / link | How MCP uses it |
|---|---|---|
| gittr Client | gittr on gittr.space · gittr.space | Same product; MCP mirrors forge actions (repos, issues, PRs, bounties) |
| gitnostr Bridge | gitnostr on gittr.space · `git.gittr.space` | pushToBridge, file list, merge clones over HTTPS |
| Pages / nsite | nsite-gateway · `pages.gittr.space` | Out of band for most MCP git tools |
| Blossom | gittr-blossom · `blossom.gittr.space` | Blob storage Pages uploads land on |
| gittr Pyramid relay | pyramid · `relay.gittr.space` | Prefer in relay lists when publishing NIP-34 |
| ★ gittr-mcp (this README) | gittr-mcp on gittr.space | You are here |
| git remote nostr | ngit-cli | Not required for MCP; agents usually use bridge HTTPS + events |
Addressing for agents: resolveRepoByNostrId(npub|hex, repo) → cloneUrl + relays. Prefer announced npub-path HTTPS on `git.gittr.space` (NIP-34); hex path is a disk fallback if a symlink is missing. Include `wss://relay.gittr.space` when publishing.
What you can do (workflows)
These are the processes people actually run; each maps to MCP tools the agent can call. Agents: follow docs/AGENT-WORKFLOW.md (which tool, and what not to call after it).
Ship a new project
- `createRepo` — push initial files to the bridge and publish Nostr kinds 30617 + 30618 in one step (best default for agents). Pass `publicRead: false` to create a private repo (code/clone/API/SSH readable only by you and listed maintainers). The announcement name/description still appear on relays — only file access is gated.
- Or step-by-step: `pushToBridge` → `publishRepoAnnouncement` → `publishRepoState`.
Private repositories
- Set `publicRead: false` on `createRepo`, `publishRepoAnnouncement`, `forkRepo`, or `mirrorRepo`.
- Private repos are hidden from Explore/home/profile listings for strangers.
- Direct URL still shows the repo name with a Private badge; unauthorized viewers see a lock screen (no code).
- SSH / CLI / API reads use the same ACL as the web UI: your npub must be owner or maintainer (
addCollaboratoror Settings → Contributors on gittr.space). - SSH key registration is unchanged — keys identify *you*; private repos only check whether *your pubkey* has read permission.
Day-to-day development
- `pushToBridge` — update files on a branch (NIP-98 auth to gittr bridge); optional `deletedPaths` / `allowTreeShrink` for file or folder deletes (parity with Code-tab trash).
- `getFile`, `bridgeListFiles`, `bridgeGetFileContent`, `getBranches`, `getCommitHistory` — read without cloning.
getFileis the bridge, then a short GRASP list — not the Code tab. On the website: latest live 30617; forge `source` is the tree when present (stale bridge listing is replaced); otherwise first non-emptyclone[]listing. See MCP-GITTR-PARITY.md and gittr FILE_FETCHING_INSIGHTS.md. - `resolveRepoByNostrId` — find clone URLs and relays from npub + repo name.
Issues (bug reports, tasks)
- `listIssues`, `getIssueById` — same rows as the website Issues tab. Nostr issues, plus GitHub or Codeberg/Gitea issues when the repo source says so. They stay separate rows.
getIssueByIdwithissue-Nor a number needs `ownerPubkey` and `repoId`. GitLab sources stay Nostr-only. - `createIssue`
- `listIssueComments`, `createIssueComment` — Nostr comments on a 64-character id. Forge comments when the id is
issue-Nor a number (read-only; the website does not post them back to GitHub). - `closeIssue`, `reopenIssue` — publish NIP-34 status events (1632 / 1630) for a 64-char Nostr event id. GitHub/Gitea imported
issue-12/pr-12(and a bare12) are refused — close those on the origin.
Pull requests (code review flow)
| Step | Tool | Notes |
|---|---|---|
| List / open PR | `listPRs`, `createPR` | List matches the website: Nostr kind 1618 plus GitHub or Codeberg/Gitea pr-N when the repo has that source. createPR publishes the Nostr event. |
| Comment on PR | `listPRComments`, `createPRComment` | Nostr comments on a 64-character id. pr-N reads the forge conversation (needs ownerPubkey and repoId). Not written back to GitHub. |
| Full PR with git branches | `createPRViaGittrCLI` | Recommended when the agent has `git` on PATH. |
| Update PR tip | `updatePullRequest` | New commit + clone URLs on the PR event. |
Merge into main | `mergePullRequest` | Real git merge of a Nostr PR (kind 1618 event id): clone/fetch, merge, push bridge, publish 30618 + merged status 1631. Forge pr-N is refused. Repo owner or listed maintainer; `git` required. |
| Mark merged (Nostr only) | `markPullRequestMerged` | Status only — no git merge. |
Honest limits on PRs: Creating and listing PRs via MCP is supported. Merging needs `git` installed and permission on the repo. Some relays are strict about clone URL + relay matching in repo announcements — if PR publish fails, fix metadata (see Limitations) or use `createPRViaGittrCLI`. Details: docs/DEVELOPER.md#limitations.
Fork, mirror, import
- `forkRepo` — fork an existing gittr repo under your key.
- `mirrorRepo` — same result as the website Push of a GitHub/GitLab repo: forge commits on gittr (history kept, and a later call updates them), the same git-server list, and a state event whose
HEADis the forge default branch. A later call keeps the name, description, and web links already announced. - `importRemoteToBridge` — copy onto the git server only. With the owner key, a later call updates the forge commits. It does not publish the Nostr card. Use `mirrorRepo` for the full website result.
- Forge 403 / suspended account: if the repo was already copied, keep using
https://git.gittr.space/ / .git. Do not pointmirrorRepoat a new forge to change the source — that copies the new URL onto gittr and replaces the branches. Guide: docs/AGENT-WORKFLOW.md.
Discover & social
- `listRepos`, `searchRepos`, `myRepos`, `exploreRepos`, `getTrendingRepos` (trending = recent repos, not engagement rank)
- `starRepo`, `unstarRepo`, `listStars` — NIP-25 on the repo’s 30617 event (same as gittr Star button).
- `watchRepo`, `unwatchRepo`, `listWatchedRepos` — NIP-51 kind 10018 followed-repo list (same as gittr Watch).
- `getRepoContributors`
Parity details: docs/MCP-GITTR-PARITY.md — what matches gittr.space vs caveats.
Releases & tags
- `listReleases` — git tags from bridge (
refs/tags/*), not the web UI Releases tab and not Zapstore. - `listForgeReleases` — forge Releases tab listing (all assets; no NIP-82 MIME gate).
- `createRelease` — returns guidance only (UI release notes until next 30617 push).
- `fetchForgeReleases` — one forge Release + announceable binaries. Omit
tagfor latest;hash:truefor sha256 (required before announce). - `announceSoftwareFromForgeRelease` — Zapstore/NIP-82 (kinds 32267 / 30063 / 3063) from a tagged forge Release. APK preferred; AppImage/DMG/linux
tar.gz/MSI/EXE/IPA also. Extra binaries on the same tag are sibling assets. Copiesimages:from the forgezapstore.yaml. OptionalpinToBlossom(public Blossom;blossom.gittr.spaceonly for officialspace.gittr.app). Same as gittr Nostr Apps (latest) or Releases Announce on Nostr (tag=). Never a tagless app. - `deleteSoftwareAnnounce` — NIP-09 kind 5 for th