Wavedash
io.github.wvdsh/wavedash · v0.1.0
Wavedash docs and workflow guidance for building and publishing browser games.
MCPremoteno credentialsEntertainment & gamesWeb search & scrapingDocuments & PDF
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 4 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 4 tools · 4 read, 0 write · Web search & scraping, E-commerce, Documents & PDF
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://mcp.wavedash.com/mcpTools
4 tools listed at last check
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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.wvdsh/wavedash)