wawesome

io.wawesome由 wawesome.io 发布官方发布者v0.1.0更新于 Oct 24, 2026

Deploy JavaScript Functions and static sites, read logs, and roll back on wawesome.

已验证Streamable HTTP可网页运行云端与基础设施开发者工具

概览

AI 生成的概览

远程 wawesome MCP 端点，让助手部署 JavaScript Functions 与静态站点、读取日志、诊断故障并回滚版本。

可以做什么
  • 列出 App 与 Function，查看某个 Version 正在运行的源码
  • 把代码与静态文件一起部署，调用 handler，并从线上站点取回页面
  • 读取调用日志并诊断最近一次失败
  • 回滚 Version，设置环境变量
  • 为本地磁盘上的文件申请上传链接
  • 自定义域名只能通过控制台或 CLI 绑定，端点不提供
适用场景
适合在构建或维护 wawesome App 时，直接在对话里部署、查看、调试或回滚 Function 与静态页面，而不必打开控制台。需要框架构建的项目必须改用 CLI，因为平台本身不做构建。
运行要求
远程端点 streamable HTTP；首次调用工具时通过 GitHub 或 Google 完成 OAuth 登录，授权页也可顺带创建工作区。可选的 CLI 需要 Node 22.13 或更高版本。
安装前请注意
授权页选择的权限范围决定该连接能做什么：部署与回读范围包含部署、回滚、调用 handler、取回页面和设置环境变量，会改动线上站点。该连接是工作区中的一项凭据，可在 Workspace Settings 中撤销。任何范围都不会绑定自定义域名。

安装

在 SourceWeft 中

  1. 打开 控制台中的 wawesome，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.wawesome%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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

/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.

SkillWhat it is for
wawesome-setupThe consent screen's three jobs, which tools each one carries, and what to do when a tool refuses
wawesome-platformWhat a deploy can carry from a chat, how to check what is live, and the work that belongs to the dashboard
wawesome-cliDeploying 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

bash
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.

来源：README.md，提交 85c7b84

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.1.0最新Sep 25, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分