Wavedash

io.github.wvdshPublished by GitHub account wvdshv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Read-only remote MCP server that lets an assistant search Wavedash docs, plan browser-game SDK integration, and validate wavedash.toml config.

What you can do
Search and fetch official Wavedash documentation pages as Markdown, including SDK, engine, CLI and config topics, with ranked results and excerpts. Plan a Wavedash integration stage by stage: architecture and reading order, CLI setup and local testing, SDK feature reference, or upload and release checklist. Validate wavedash.toml text pasted from chat for missing game_id or upload_dir, entrypoint and upload_dir conflicts, absolute paths and engine sections.
When to use it
Use it when building or publishing a browser game on Wavedash and you want the assistant to follow official docs, engine setup steps and publishing checklists instead of guessing. Also useful for checking a wavedash.toml before running the CLI.
Requirements
A remote Streamable HTTP endpoint; no account, API key or environment variable is needed. Local MCP clients that expect stdio can bridge to it with mcp-remote. Network access to the Wavedash docs site is required.
Before you install
The server is unauthenticated and read-only: it cannot upload, publish or access accounts, builds or private data. Do not pass API keys, session cookies or other credentials as tool arguments; authenticated steps such as CLI login, upload and publishing must be done separately by the user.

Installation

In SourceWeft

  1. Open Wavedash in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wvdsh%2Fwavedash/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wavedash": {
      "type": "http",
      "url": "https://mcp.wavedash.com/mcp"
    }
  }
}

README

Wavedash MCP

Read-only remote MCP server for Wavedash docs, SDK guidance, engine setup, and publishing checklists.

This server is intentionally unauthenticated. It only reads public docs from https://docs.wavedash.com and does not access user accounts, games, builds, local files, API keys, or private Wavedash data.

Tools

Four orthogonal tools, so clients rarely have to choose between overlapping options:

  • wavedash_implementation_planner - plan and guide a Wavedash integration from the user's goal, engine, and requested features. The stage argument selects 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 pages with content, as text and as structured output.
  • search_wavedash_docs - search official Wavedash docs.
  • get_wavedash_doc - fetch a docs page as Markdown.
  • validate_wavedash_config - validate wavedash.toml text, including single-line or fenced input pasted from chat.

Engine, topic, and feature pages are resolved at runtime from the docs site's search index, so new docs pages need no change here.

Run Locally

bash
npm installnpm start

The MCP endpoint is:

text
http://localhost:3000/mcp

Health/info endpoint:

text
http://localhost:3000/

Docker

bash
docker build -t wavedash-mcp .docker run --rm -p 3000:3000 wavedash-mcp

Cloudflare Workers

The Worker entrypoint is src/worker.js, configured by wrangler.toml. It serves a stateless Streamable HTTP MCP endpoint at /mcp.

The Deploy MCP to Production GitHub Actions workflow deploys automatically on pushes to main that change MCP source, package dependencies, wrangler.toml, the root package.json, or the deployment workflow itself. Documentation and skill changes do not trigger deployment. Manual workflow runs remain available.

Local Worker dev:

bash
npm run worker:dev

Validate the Worker bundle without publishing:

bash
npm run deploy:dry-run

Deploy:

bash
npm run deploy

From the repo root, use:

bash
npm run mcp:deploy

The production MCP endpoint is:

text
https://mcp.wavedash.com/mcp

wrangler.toml declares mcp.wavedash.com as a Cloudflare Workers Custom Domain. If wavedash.com is in the same Cloudflare account, Wrangler can attach the hostname without a manual DNS record.

Remote Client Testing

Health/info endpoint:

text
https://mcp.wavedash.com/

Cloudflare AI Playground can test the deployed endpoint directly:

text
https://mcp.wavedash.com/mcp

Remote MCP clients that support Streamable HTTP can connect directly to the same endpoint.

For Claude Desktop or other local MCP clients that expect stdio, use mcp-remote:

json
{  "mcpServers": {    "wavedash": {      "command": "npx",      "args": ["mcp-remote", "https://mcp.wavedash.com/mcp"]    }  }}

Configuration

Environment variableDefaultDescription
PORT3000HTTP server port.
WAVEDASH_DOCS_BASE_URLhttps://docs.wavedash.comPublic docs origin.
WAVEDASH_MCP_FETCH_TIMEOUT_MS10000Fetch timeout for docs requests.
WAVEDASH_MCP_SEARCH_CACHE_MS300000Search index cache TTL.

v0 / Lovable / Bolt Scope

Use this server as a no-auth Wavedash MCP listing. It can guide agents while they generate browser games, but it cannot upload or publish builds.

For authenticated steps, the MCP should instruct the human or host agent to use:

  • Wavedash CLI install docs: https://docs.wavedash.com/cli/installation
  • Wavedash CLI browser login: wavedash auth login
  • CI/API token login: wavedash auth login --token ... or WAVEDASH_TOKEN
  • Developer Portal manual upload/publish: https://wavedash.com/dev-portal

The Wavedash CLI is the command-line app for signing in, initializing wavedash.toml, testing locally, uploading builds, and publishing from a project folder. For users who do not want terminal commands, route them to the Developer Portal instead.

Do not pass API keys, session cookies, or private credentials as MCP tool arguments.

Authenticated tools such as creating games, uploading builds, or publishing should live in a separate authenticated MCP surface backed by Wavedash OAuth or scoped agent grants.

Source: mcp/README.md at commit 0a0f76e

Tools

4

wavedash_implementation_planner

Plan Wavedash Implementation

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.

Parametersgoalrequiredstageenginefeatures

search_wavedash_docs

Search Wavedash Docs

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.

Parameterslimitqueryrequired

get_wavedash_doc

Get Wavedash Doc

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.

Parameterspathrequired

validate_wavedash_config

Validate Wavedash Config

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.

Parameterstomlrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts