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 Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 16/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect gittr-mcp yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect gittr-mcp yet
The maker has not listed install details in the MCP Registry yet
What you can do instead
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code cannot connect gittr-mcp yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect gittr-mcp yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect gittr-mcp yet
The maker has not listed install details in the MCP Registry yet
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Connection
- –
- Latest versioni
- 1.0.2
- Categoryi
- Developer tools
- Published to registryi
- Jul 13, 2026
- Code last changedi
- Nov 15, 2026
- Maker
- arbadacarbaYK
- Website
- gittr.space
- Registry status
- Active
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account arbadacarbaYK, which owns the repo
- ✓ Pass
Still maintained
Code last changed 4 days ago
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/arbadacarbayk-gittr-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 69% of the other 6136 servers in this category
- Published to the registry more recently than 19% of the other 6136 servers in this category
- Basic checks equal to or better than 99% of the other 6136 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is gittr-mcp safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 4 days ago, and the latest version (1.0.2) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Cloudflare MCP
Cloudflare MCP servers
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.
| This one gittr-mcp | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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