GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Beschreibung vom Entwickler (englisches Original)
Get open-source GitHub projects running on your computer, with your AI app
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://mcp.usegithubthing.com/mcpDie .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
claude mcp add --transport http ugt https://mcp.usegithubthing.com/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"ugt": {
"url": "https://mcp.usegithubthing.com/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"ugt": {
"type": "http",
"url": "https://mcp.usegithubthing.com/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://mcp.usegithubthing.com/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
search_recipesFind how UGT gets a job done on the user's own computer with open-source software from GitHub, such as subtitles, CAD, video or web pages to Markdown. Search by what the user wants done or by a project's name, or omit the query to list the newest recipes. A recipe is a verified w
get_projectGet how UGT runs one GitHub project, by owner/repo or its link: the recipes people have shared for it, each verified for one job. Every GitHub project works with UGT, so the result always says what to do next.
get_recipeGet one recipe in full: what it takes and makes, what stays usable after a run, the settings it asks for, everything it can reach and why, where it was tested, and every file it runs.
read_recipe_fileRead one of a recipe's files, such as compose.yaml, its Dockerfile or recipe.json, to see exactly what it runs.
get_installGet the one line that installs UGT on the user's Windows PC, Mac or Linux computer and connects it to their AI apps, UGT for Claude Desktop, and what each computer runs recipes in. Omit the computer to get every one.
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 6. Nov. 2026
Der Herausgeber (usegithubthing.com) ist nicht der Repo-Inhaber (auscaster); vielleicht hat jemand anderes ihn eingetragen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 533 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 5 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 2 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.
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.3.0) kam gestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: GitHub, Desktop Commander, Cloudflare MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
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.
You found it on GitHub. Now use it.
Paste the GitHub link to the project you want to use.
UGT helps get it working on your computer and shows you how to use it again.
Free and open source. Windows, Mac and Linux.
How it works · Get started · What you can do · Why not just ask your agent? · The catalogue · Share your recipe · House rules
Paste your GitHub project into UGT. The link is enough. If you already tried to install it, you can include the error you saw.
UGT checks for a way to use that project on your computer. If it offers Open in UGT, open it, choose your file if it needs one, and run it. When a file is ready, UGT shows you its folder. An app opens at its own address.
If the project needs a closer look, continue in your desktop AI app. The website carries your link and notes into the project message. If UGT needs installing, it shows how to set it up. UGT has no subscription; your AI app's own usage limits and pricing still apply.
Set up UGT yourself
curl -fsSL https://usegithubthing.com/install | sh.irm https://usegithubthing.com/install.ps1 | iex. Windows may ask for permission and a restart.Return to your project when setup finishes. On an Intel Mac, start Docker Desktop, OrbStack or Docker Engine first.
For developers
| Where | How | ||
|---|---|---|---|
| Windows | scoop bucket add auscaster https://github.com/auscaster/scoop-bucket, then scoop install ugt | Today | |
| Windows | winget install auscaster.ugt | Next | |
| macOS or Linux | brew install auscaster/tap/ugt | Today | |
| Linux | `curl -fsSL https://usegithubthing.com/install \ | sh` | Today |
| Any MCP client | com.usegithubthing/ugt in the MCP Registry, or ugt mcp over stdio | Today | |
| Any AI app, with nothing installed | The hosted MCP server https://mcp.usegithubthing.com/mcp: it finds how UGT runs a project, shows what a recipe runs and reaches, and gives the line that installs UGT | Today | |
| Claude Code, Codex, Gemini CLI | UGT's plugin: claude plugin install ugt@auscaster after claude plugin marketplace add auscaster/agent-plugins, the same for Codex, or gemini extensions install https://github.com/auscaster/ugt | Today | |
| Your browser | A "Use it" button on every GitHub repository | Next | |
| From source, any OS | go install github.com/auscaster/ugt/cmd/ugt@latest, then ugt setup and ugt connect | Today |
GitHub is the world's biggest shelf of free software, and most of it never reaches the people it could help, because it ships as code, not as an app. UGT turns any of it into something you can just ask for.
| Ask your agent | What runs |
|---|---|
| "Put subtitles on this interview" | openai/whisper: speech to text, fully offline. Verified recipe |
| "Turn my HTML into a four-second intro video" | heygen-com/hyperframes: a headless browser and ffmpeg. Verified recipe |
| "Design a wall hook I can 3D print" | earthtojake/text-to-cad: an industrial CAD kernel. Verified recipe |
| "Save these pages as clean Markdown, on my own computer" | firecrawl/firecrawl: a five-service crawler stack. Verified recipe |
| "Cut the background out of this photo" | danielgatis/rembg: an image segmentation model |
| "Convert this PDF and Word file to Markdown" | microsoft/markitdown: Microsoft's document converter |
| "Read this paragraph aloud" | debpalash/VoiceStudio: local text to speech |
| "List the functions in this program" | NationalSecurityAgency/ghidra: the NSA's reverse-engineering suite, headless |
A few featured examples. You never need a recipe from the catalogue: without one, your agent works the project out the first time. A recipe just makes it faster, because someone already did.
Your agent can read the code. It usually can't run it for you, and it starts from zero every time.
Recipes are a shortcut, never a requirement. Each one is a project someone already got doing a job, shared so nobody has to work it out again. A recipe is a folder anyone can read, in recipes/: a compose.yaml that holds everything that runs, and a recipe.json that says what it does. One project can have many recipes, one per job.
Browse them at usegithubthing.com/recipes, or read their source in recipes/. Every one was verified on clean machines before it was admitted, and a new recipe works for everyone the moment it lands, with no update to UGT.
Verified means every service ran as written on clean amd64 and arm64 machines and passed both checks, and both checks rejected deliberately broken outputs. A featured recipe's image is the one that was verified; any other builds on your machine from the same pinned commit and bases.
What's inside a recipe
recipes/openai/whisper/subtitles/
compose.yaml everything that runs: build, limits, mounts, network, and the four services recipe.json what it is: project, commit, task, settings, the access it needs, licence Dockerfile fetches the pinned source itself, so the build needs no clone check/ the check scripts
| Service | Does |
|---|---|
task | Your job, on your files |
check | Fails unless the job really happened, whatever your input was |
sample | Puts a known input in place |
sample-check | Fails unless the known input gave the known answer |
It is plain Compose, so there is no new language to learn, and every recipe runs anywhere Compose does. The recipe reference has the rules.
Got a project doing something useful? Share it, so the next person gets it fast instead of working it out again.
Tell your AI "Use the GitHub Thing: share this recipe", or run ugt recipe submit. UGT checks it runs again from scratch, makes sure nothing personal goes with it (your files, paths and keys), and opens a pull request as you. It is then verified on clean machines with no secrets available, and admitted once it passes; a maintainer reviews any recipe that reaches beyond its sandbox first.
Coming with the UGT app. Until then, from the source:
go install github.com/auscaster/ugt/cmd/ugt@latest
ugt recipe new / # start one, or adopt the project's own Compose file ugt recipe verify # until it passes ugt login # once: approve a code in your browser ugt recipe submit # opens the pull request as you
ugt recipe submit --dry-run shows exactly what would be sent first. CONTRIBUTING.md and the catalogue rules have the details.
Maintain a project? A "Run with UGT" badge is on the way: put it in your README, and one click opens your project in UGT.
Nur der Anfang wird gezeigt; den Rest findest du im Repo