GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者による説明(英語の原文)
Get open-source GitHub projects running on your computer, with your AI app
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://mcp.usegithubthing.com/mcpリンク先は作者自身のファイルです。私たちが置いたり再パッケージしたりしたものではありません。ファイルを開くと、Claude Desktopがインストールします。
ターミナルでこれを実行します
claude mcp add --transport http ugt https://mcp.usegithubthing.com/mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"ugt": {
"url": "https://mcp.usegithubthing.com/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"ugt": {
"type": "http",
"url": "https://mcp.usegithubthing.com/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://mcp.usegithubthing.com/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
ツールの名前と説明は、サーバーが2026年11月6日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
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.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
公開者(usegithubthing.com)がリポジトリの所有者(auscaster)ではありません。別の人が登録した可能性があります
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
533ミリ秒で応答(HTTP 200)
サインイン不要
5件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち2項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。
GitHubリポジトリの最終更新は–、最新バージョン(0.3.0)がレジストリに届いたのは昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:GitHub, Desktop Commander, Cloudflare MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
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
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
冒頭だけを表示しています。続きはリポジトリで読めます