mcp server
Wavedash
Wavedash docs and workflow guidance for building and publishing browser games.
Description as published by the maintainer. Source
- version 0.1.0
- active
- browser automation
active — Registry entry last updated 2026-06-29. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
wavedash_get_agent_workflow(engine, features)- Return a concise end-to-end workflow for AI agents creating a browser game from scratch and preparing it for Wavedash upload. Read-only and unauthenticated; upload still happens through the Wavedash CLI or Developer Portal.
wavedash_get_doc(path)- Fetch a full Wavedash docs page as Markdown by path or docs.wavedash.com URL. Read-only and unauthenticated. Required: path.
wavedash_get_publishing_checklist(engine)- Return Wavedash upload and publishing checklist guidance, optionally including an engine-specific docs page. Read-only and unauthenticated.
wavedash_get_quickstart(engine, features)- Return the Wavedash setup path for a browser game, optionally including an engine and SDK features. Read-only and unauthenticated.
wavedash_get_sdk_reference(topic)- Fetch Wavedash SDK docs for a specific feature such as setup, multiplayer, achievements, leaderboards, cloud saves, UGC, players, events, or types. Read-only and unauthenticated. Required: topic.
wavedash_implementation_planner(goal, engine, features)- Plan a Wavedash game implementation from the user's goal, engine, and requested features. Use this before making architecture claims, selecting SDK features, or writing Wavedash integration code. Read-only and unauthenticated. Required: goal.
wavedash_search_docs(limit, query)- Search official Wavedash docs for browser game development, SDK integration, engines, CLI, upload, and publishing. Read-only and unauthenticated. Required: query.
wavedash_validate_config(toml)- Validate pasted wavedash.toml text for basic Wavedash CLI config issues. This does not read files; provide the config text as input. Required: toml.
Last successful function declaration observed on . Source: https://mcp.wavedash.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.wavedash.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-29 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-29 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.wavedash.com | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | mcp.wavedash.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json