wawesome
io.wawesomePublished by wawesome.ioOfficial publisherv0.1.0Updated Oct 24, 2026
Deploy JavaScript Functions and static sites, read logs, and roll back on wawesome.
Overview
Remote wawesome MCP endpoint that lets an assistant deploy JavaScript Functions and static sites, read logs, diagnose failures and roll back versions.
- What you can do
- List Apps and Functions and inspect the source a Version is running
- Deploy code and static files together, invoke a handler, and fetch a page back from the live site
- Read invocation logs and diagnose the latest failure
- Roll a Version back and set environment variables
- Request an upload link for files on your own disk
- Attach custom domains only through the dashboard or CLI, not the endpoint
- When to use it
- Useful when you build or maintain wawesome Apps and want to deploy, inspect, debug or roll back Functions and static pages from the chat instead of the dashboard. Projects that need a framework build must use the CLI, since the platform builds nothing.
- Requirements
- Remote endpoint at over streamable HTTP, with OAuth sign-in through GitHub or Google on the first tool call; the consent screen also creates a workspace if you have none. The optional CLI needs Node 22.13 or newer.
Installation
In SourceWeft
- Open wawesome in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.wawesome%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"wawesome": {
"type": "http",
"url": "https://api.wawesome.io/v1/mcp"
}
}
}README
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
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.
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
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.
Source: README.md at commit 85c7b84
Tools
0Version history
1- v0.1.0LatestSep 25, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts