GitHub
de github
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Computadora o nube★ 34.245MITActualizado hace 4 días
Instalar
UGT: Use the GitHub Thing
Resumen
Descripción del creador (original en inglés)
Get open-source GitHub projects running on your computer, with your AI app
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi2 de 3 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Computadora o nube
- Transporte: stdio, Streamable HTTP
- Categoría: Herramientas para desarrolladores
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 2 de 3 superadas
- Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
- Puede hacer 5 cosas (herramientas) search_recipes, get_project, get_recipe, read_recipe_file …
- El registro no indica ninguna clave que completar.
Necesitas
- Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
- Abre Settings → Connectors
- Presiona Add custom connector
- Pega la dirección de abajo y presiona Add
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://mcp.usegithubthing.com/mcpDescargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
claude mcp add --transport http ugt https://mcp.usegithubthing.com/mcpO copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"ugt": {
"url": "https://mcp.usegithubthing.com/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"ugt": {
"type": "http",
"url": "https://mcp.usegithubthing.com/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
- Abre ChatGPT en la web → Settings → Connectors (Apps)
- Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
- Pega la dirección de abajo, ponle un nombre y guarda
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://mcp.usegithubthing.com/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
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.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
- ! Precaución
El creador coincide con el repo
Quien lo publicó (usegithubthing.com) no es el dueño del repo (auscaster); puede que otra persona lo haya listado
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- ✓ Superada
El endpoint responde
Respondió en 533 ms (HTTP 200)
- – No aplica
Inicio de sesión con OAuth
No hace falta iniciar sesión
- ✓ Superada
Sin instrucciones ocultas en las descripciones de herramientas
Leímos 5 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con otros en Herramientas para desarrolladoresi
- Más estrellas que el 0% de los otros 1395 servidores de esta categoría
- Publicado en el registro más recientemente que el 95% de los otros 1395 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 25% de los otros 1395 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro UGT: Use the GitHub Thing?
Superó 2 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.3.0) llegó al registro anteayer.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
¿Qué puedo usar en su lugar?
En la misma categoría: GitHub, Desktop Commander, Cloudflare MCP
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Desktop Commander
de wonderwhy-er
MCP server for terminal commands, file operations, and process management
Se ejecuta en tu computadora★ 10.225MITActualizado hace 16 días
Instalar
Cloudflare MCP
de cloudflare
Cloudflare MCP servers
Se ejecuta en la nube★ 4446Apache-2.0Actualizado hace 14 meses
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
How it works
- Start with the GitHub link. You can also add an error you ran into or something you want to do with the project.
- Follow the setup for your computer. UGT looks for a ready setup or the project's own installer. If it needs a closer look, your AI app continues with the same link and details. A recipe is a setup someone has already checked; your agent can make one when the project has none.
- Use what it made. Open the resulting file or app. File jobs check their output, and apps keep their saved data when you stop and reopen them. If a run fails, ask for help with that run without starting the conversation over.
- Share it, if you like. Once it works, UGT can submit your recipe to the catalogue, so the next person gets it fast.
Get started
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
- Claude Desktop: install the UGT desktop extension for your computer. The project page helps you pick the download.
- On a Mac or Linux: open Terminal and run
curl -fsSL https://usegithubthing.com/install | sh. - On Windows: open PowerShell and run
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 |
What you can do with it
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.
Why not just ask your agent?
Your agent can read the code. It usually can't run it for you, and it starts from zero every time.
- Most of GitHub assumes Linux. On Windows and on a Mac your agent hits a wall. UGT brings its own private Linux engine, set up in one step, on Linux too: no Docker Desktop, no account, nothing to learn. On an Intel Mac it drives the engine you already have.
- Proven once, quick for everyone after. The first agent to get a project working can spend an hour building and fixing: memory limits, wrong-architecture binaries, missing system libraries, a resolver that cannot find the internet. The recipe it leaves behind turns the next person's run into a download.
- Proof, not "it started". A container starting is not your job done. Every recipe carries a check that fails unless the output is real: subtitles that fit the recording, a video of the length you asked for, a mesh you can actually print.
- Your machine, your files. Projects run in a sandbox with only the files and access their recipe declares. The catalogue reviews that access before admitting a recipe; UGT asks before a locally made recipe reaches beyond its ordinary sandbox. Cloud compute requires your agreement and a stated cost.
The catalogue
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.
Share your recipe
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@latestugt 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.
House rules
- Your files stay yours. Inputs are copied in. Your home folder, keys and the container engine are never handed to a project unless its recipe says why and a maintainer reviewed it, or you agree.
- Run anything, hide nothing. A recipe can need the internet, a folder, a device or more. It declares each one, and UGT refuses anything it did not declare. A maintainer reviews it before the catalogue admits it; a recipe from anywhere else asks you before it reaches your computer.
- Proof or it didn't happen. No check, no success.
- You decide. Installs, admin prompts, big downloads, accounts, keys and cloud compute are always your call, asked plainly before they happen.
- Secrets never pass through your agent. UGT asks you for them itself, once, and they live in your system keychain.
- Credit travels with the code. Every recipe records its project's licence, and files adapted from upstream keep theirs.
- **Your files never leave your
Solo se muestra el principio; lee el resto en el repo