GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Deploy JavaScript Functions and static sites, read logs, and roll back on wawesome.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.wawesome.io/v1/mcp在终端中运行这条命令
claude mcp add --transport http wawesome https://api.wawesome.io/v1/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"wawesome": {
"url": "https://api.wawesome.io/v1/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"wawesome": {
"type": "http",
"url": "https://api.wawesome.io/v1/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.wawesome.io/v1/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 wawesome.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.0)于43天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况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、图片和脚本已被移除。链接会离开本站。
Deploy JavaScript Functions and static pages to wawesome without leaving Claude Code.
An App holds Functions. A Function is one JavaScript module whose default export has a fetch handler, and the static files a deploy carries are served beside it. There is no build step and no bundler, so a deploy serves exactly what it declared.
/plugin marketplace add wawesomeio/claude-plugin
/plugin install wawesome@wawesome
Once the plugin is in Anthropic's directory, /plugin install wawesome works on its own.
The first tool call opens a browser tab on auth.wawesome.io. Sign in with GitHub or Google, and pick what the connection may do. If you have no wawesome workspace yet, that screen creates one. Installing the plugin is the whole of signing up.
There is no client ID and no client secret to enter anywhere, and you are never asked to paste a token into a chat.
The MCP endpoint, https://api.wawesome.io/v1/mcp. It lists your Apps and Functions, answers the source a Version is running, deploys code and files together, invokes a handler, fetches a page back off the live site, reads invocation logs, diagnoses the latest failure, rolls a Version back, sets environment variables and attaches custom domains.
Three skills, which Claude reads when the work calls for them.
| Skill | What it is for |
|---|---|
wawesome-setup | The consent screen's three jobs, which tools each one carries, and what to do when a tool refuses |
wawesome-platform | What a deploy can carry from a chat, how to check what is live, and the work that belongs to the dashboard |
wawesome-cli | Deploying a project that runs a framework build |
Two commands. /wawesome-deploy deploys this project and fetches the result back. /wawesome-diagnose works out why a Function is failing.
The endpoint does nearly everything, and it does it better: one round trip, structured answers, no shell.
The CLI covers the one thing the endpoint cannot. A project that runs a framework build has to be built somewhere, and the platform builds nothing. So npx wawesome deploy runs the build on your machine and uploads what it wrote. That is the only trigger. Files on your own disk are not one: ask for them in the conversation and the agent calls request_upload, which answers a link that opens for you and nobody else.
The CLI needs Node 22.13 or newer and nothing else.
.mcp.json cannot ask for a scope, so you pick a job on the consent screen yourself:
None of the three attaches a custom domain. That is done on the dashboard or from the CLI.
The connection is one credential in your workspace, listed at Workspace Settings, then Credentials. Revoke it there and its very next call is refused.
claude plugin validate --strict .
Every pull request runs that. main is protected, because a push to this repository reaches the plugin directory with nothing in between.
MIT. See LICENSE.