All servers · APIs & integrations · Build & deploy
Wavedash
io.github.wvdsh/wavedash · v0.1.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | resources, tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Wavedash docs and workflow guidance for building and publishing browser games.
Connect
streamable-http · https://mcp.wavedash.com/mcp
claude mcp add --transport http wavedash https://mcp.wavedash.com/mcp{
"mcpServers": {
"wavedash": {
"url": "https://mcp.wavedash.com/mcp"
}
}
}Tools as reported by the server
wavedash_implementation_plannerPlan and guide a Wavedash browser game integration from the user's goal, engine, and requested features. Call this first for any request to build, deploy, upload, or release a game on Wavedash, or to add Wavedash SDK features. Choose the stage: plan (architecture and reading order), setup (CLI instasearch_wavedash_docsSearch official Wavedash docs (docs.wavedash.com) for browser game development, SDK integration, engines, CLI, upload, and publishing. Use this instead of web search for any Wavedash question when the exact page is unknown. Returns ranked pages with paths, URLs, and excerpts. Read-only and unauthentget_wavedash_docFetch a full Wavedash docs page as Markdown by path or docs.wavedash.com URL, for example sdk/achievements, engines/unity, or cli/configuration. Use this when the user wants to see a Wavedash docs page or when exact SDK, CLI, or config details are needed. Only docs.wavedash.com pages can be fetched.validate_wavedash_configValidate wavedash.toml contents for Wavedash CLI config issues (missing game_id or upload_dir, entrypoint repeating the upload_dir, absolute paths, engine sections). Call this whenever the user shares wavedash.toml text or asks to check their Wavedash config, even if the problem looks obvious. Accep
Repository · Website · JSON · Text for agents · Registry updated 2026-06-29