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 分