Skip to content

Wavedash

by wvdsh · remote · no sign-in to list tools · v0.1.0 · published by GitHub user wvdsh

Wavedash docs and workflow guidance for building and publishing browser games.

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http wavedash https://mcp.wavedash.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • wavedash_implementation_plannerPlan and guide a Wavedash browser game integration from the user's goal, engine, and requested features.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Plan 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 install, sign-in, SDK init, wavedash.toml, local testing), features (SDK reference for the requested features), or deploy (upload and release checklist). Returns ordered steps, boundaries, and the relevant docs.wavedash.com pages with content. Read-only and unauthenticated.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
Only reads 3Claude Code: allow
  • get_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.No findings

    Why it is in this group

    • The name "get_wavedash_doc" says "get": a word for reading.
    Description, as the server wrote it
    Fetch 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. Read-only and unauthenticated.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
  • search_wavedash_docsSearch official Wavedash docs (docs.wavedash.com) for browser game development, SDK integration, engines, CLI, upload, and publishing.No findings

    Why it is in this group

    • The name "search_wavedash_docs" says "search": a word for reading.
    Description, as the server wrote it
    Search 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 unauthenticated.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
  • 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).No findings

    Why it is in this group

    • The name "validate_wavedash_config" says "validate": a word for reading.
    Description, as the server wrote it
    Validate 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. Accepts single-line or fenced input. Pass the config text as the toml argument; this does not read files.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wavedash https://mcp.wavedash.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wavedash__search_wavedash_docs",
      "mcp__wavedash__get_wavedash_doc",
      "mcp__wavedash__validate_wavedash_config"
    ],
    "ask": [
      "mcp__wavedash__wavedash_implementation_planner"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as wavedash. Review it before you use it.