The Wavedash remote MCP server lets AI agents search public Wavedash docs, fetch
engine and SDK guidance, validate pasted wavedash.toml content, and explain
the upload and publishing workflow.
Connect
Use this server URL with any MCP client that supports Streamable HTTP:
https://mcp.wavedash.com/mcp
Health/info endpoint:
https://mcp.wavedash.com/
The server is unauthenticated because it only exposes public documentation. It does not access user accounts, private projects, builds, local files, API keys, or Wavedash account data.
Tools
The server exposes four tools:
| Tool | What it does |
|---|---|
wavedash_implementation_planner | Plans and guides an 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. |
search_wavedash_docs | Searches official Wavedash docs and returns ranked pages with paths, URLs, and excerpts. |
get_wavedash_doc | Fetches a docs page as Markdown by path or docs.wavedash.com URL. |
validate_wavedash_config | Validates pasted wavedash.toml text, including single-line or fenced input. |
Engine, topic, and feature pages are resolved from this site's search index at runtime, so new docs pages are available to agents without a server change.
Authenticated steps
For authenticated actions, the MCP server tells the human which Wavedash CLI or Developer Portal step to perform. It cannot sign in, create projects, create API keys, upload builds, publish builds, or read local files.
Use the Wavedash CLI for local project actions such as authentication, initialization, local testing, build upload, and publish.