GitHub
by 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.
Computer or cloud★ 34,245MITUpdated 3 days ago
Install
wawesome
Overview
Description from the maker (original English)
Deploy JavaScript Functions and static sites, read logs, and roll back on wawesome.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
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:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://api.wawesome.io/v1/mcpRun this in your terminal
claude mcp add --transport http wawesome https://api.wawesome.io/v1/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wawesome": {
"url": "https://api.wawesome.io/v1/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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"wawesome": {
"type": "http",
"url": "https://api.wawesome.io/v1/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:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://api.wawesome.io/v1/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.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain wawesome.io (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Developer toolsi
- More stars than 0% of the other 1394 servers in this category
- Published to the registry more recently than 57% of the other 1394 servers in this category
- Basic checks equal to or better than 100% of the other 1394 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is wawesome safe?
It passed 1 of 1 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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 42 days ago.
Which apps can use it?
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.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
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
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 16 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
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.
wawesome for Claude Code
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.
Install
/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.
What you get
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 and the CLI
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.
Permissions
.mcp.json cannot ask for a scope, so you pick a job on the consent screen yourself:
- Read and investigate writes nothing.
- Ship and read back adds deploying, rolling back, invoking, fetching and setting environment variables. This is the one to pick for building.
- Build in the workspace adds pausing schedules and creating previews, which no tool on this endpoint asks for.
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.
Development
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.
Links
License
MIT. See LICENSE.