GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Setup manuals for any GitHub repo: will it run on macOS, Windows or Linux, and the exact steps.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://gitmanual.com/mcpRun this in your terminal
claude mcp add --transport http gitmanual https://gitmanual.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gitmanual": {
"url": "https://gitmanual.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gitmanual": {
"type": "http",
"url": "https://gitmanual.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://gitmanual.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
get_setup_manualHow to install or run a GitHub repository: whether it works on macOS, Windows or Linux (with reasons), ready-made downloads, install commands from the README, the parts it needs, and step-by-step commands to set it up from source. Facts come from the repo's own files, not guesses
get_setup_scriptOne script that sets the repo up on the given system: bash for macOS and Linux, PowerShell for Windows. It stops at the first error, skips what's already installed and never starts servers. Show it to the user to read before running it.
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 7, 2026
The registry name was verified with the GitHub account zainudinnoori, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 155 ms (HTTP 200)
No sign-in needed
Read 2 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
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.
gitmanual
Found it on GitHub? Get it running.
Paste any GitHub repo and get its setup manual: will it work on your device, what you need, and the exact steps for macOS, Windows or Linux.
Website · Self-hosting · Contributing · How it works
Swap hub for manual in any GitHub link:
github.com/ollama/ollama → gitmanual.com/ollama/ollama
That's it. You get a manual for the repo, written from its own files.
Plenty of people find a great project on GitHub and don't know how to run it. READMEs assume you already know which runtime, package manager, database and system it needs. gitmanual reads the repo for you and turns it into a manual a newcomer can follow.
.env settings.setup.sh or setup.ps1 (/owner/repo/setup/mac.sh, linux.sh, windows.ps1). It stops at the first error, skips what's already installed and is safe to run again. It never starts servers or runs commands that still need your own values; it lists those at the end.ANTHROPIC_API_KEY, the site writes the guide itself instead (once per repo and system, then cached).Maintainers: add a badge to your README so newcomers find the steps. Swap in your owner/repo:
[](https://gitmanual.com/ollama/ollama)
For AI assistants: an MCP server at https://gitmanual.com/mcp, listed in the MCP Registry as io.github.zainudinnoori/gitmanual. Its tools are get_setup_manual and get_setup_script; no login needed.
claude mcp add --transport http gitmanual https://gitmanual.com/mcphttps://gitmanual.com/mcp~/.cursor/mcp.json) and other clients: { "mcpServers": { "gitmanual": { "url": "https://gitmanual.com/mcp" } } }The same facts are available as JSON at /api/v1/manual?repo=owner/repo (&os=, &arch=, &format=md), and /llms.txt describes it all.
Browser extension: a Setup manual button on every GitHub repo, next to Star and Fork. Add it to Chrome (works in Edge and Brave too); the code is in extension/.
Plus the shelf (/shelf): every repo people have looked up, with search and filters for stars, language and difficulty. Every repo also gets a share image and a 1080×1080 poster.
gitmanual never clones a repo or runs its code.
raw.githubusercontent.com: the README and setup guides, package manifests, version pins, Docker and CI files, and .env examples.Analyses are cached for 12 hours, and every manual is server-rendered, so search engines can read the steps. How it works explains the verdicts and the limits in plain words.
Requires Node.js 20.9+. Or follow gitmanual's own manual, with steps and a setup script for your system.
git clone https://github.com/zainudinnoori/gitmanual.git
cd gitmanual npm install cp .env.example .env.local # optional: add a GITHUB_TOKEN (recommended) npm run dev
Open http://localhost:3000 and paste a repo. Without any settings it works out of the box: history is kept in a local SQLite file (data/gitmanual.db), and GitHub allows about 20 new repos an hour. A GitHub token raises that to thousands.
| Command | Does |
|---|---|
npm run dev | Development server |
npm run build / npm start | Production build and server |
npm run typecheck | Type check |
npm run check:scripts | Build and check the setup script of every repo in the local database (-- --add also analyzes the test list) |
All settings are environment variables, and every one is optional for local use. See .env.example and the self-hosting guide.
| Variable | What for |
|---|---|
GITHUB_TOKEN | GitHub API limit 60 → 5,000 requests/hour. Needed in production |
NEXT_PUBLIC_SITE_URL | The site's address, for canonical links, the sitemap and share images. Needed in production |
TURSO_DATABASE_URL, TURSO_AUTH_TOKEN | Hosted database for history, cache and votes. Needed in production (falls back to a local file in development) |
ANTHROPIC_API_KEY | Optional: "Write my guide" (Claude) instead of the "Ask Claude / ChatGPT" links |
NEXT_PUBLIC_REPO_URL | Your fork's GitHub URL: a GitHub link with stars in the menu, and "Report a wrong setup" |
CONTACT_FORM_URL | A ShareText form's embed link: adds "Contact" to the footer, opening the form over the page |
RATE_LIMITS, LIMIT_SALT | Limits are on by default (new analyses 40/hour per visitor and 1,000/hour in all, new AI guides 5/day and 100/day, votes once per repo and system a day). RATE_LIMITS=off turns them off; LIMIT_SALT is any random string that keeps visitor codes unguessable |
FINDS_*, FB_PAGE_*, CRON_SECRET | Optional Finds page: posts from a Facebook Page, each linked to its manual |
The quickest route is Vercel + Turso (both have free tiers): create a Turso database, add the variables above, and deploy. The step-by-step version is in docs/self-hosting.md.
app/ Pages and API routes (Next.js App Router)
[owner]/[repo]/ The manual, its share image and poster shelf/ finds/ how-it-works/ api/ analyze, guide (Claude), vote, finds, cron/facebook lib/ pipeline.ts cache → GitHub → analysis → save github.ts GitHub API and raw file downloads detect.ts Stack, versions, services and per-OS steps install.ts Release downloads and README install commands readme.ts guides.ts README sections, setup guides, scripts, docs links fit.ts platforms.ts "Will it work on my device?" os.ts Per-OS installers and PowerShell rewrites db.ts Turso / SQLite og.tsx Share images and posters facebook.ts picks.ts Optional Finds (Facebook Page sync)
The visual language (an assembly manual: ink outlines, a wrench-orange box, sticker verdicts) is described in DESIGN.md.
These are the known gaps. Help is welcome:
Wrong steps for a repo? That's the most useful bug report there is. Open an issue with the repo link, or improve a rule yourself. See CONTRIBUTING.md. Please follow the Code of Conduct, and report security issues privately (SECURITY.md).
MIT. The repos gitmanual describes keep their own licenses; it only reads their public files.