ENDPOINT 1
https://wave.co/mcp
MCP server metadata
- Name
- wave-docs
- Version
- 1.0.0
This server exposes Wave's public documentation — no account, token, or OAuth is needed, and every resource URI is also a plain HTTPS URL you can fetch directly. Start with resources/list, or call search_docs to find the section you need and read_doc to fetch it. To reach an actual user's recordings, transcripts, and action items, connect to the separate authenticated server at https://mcp.wave.co (OAuth 2.0 with PKCE, or a wave_mcp_ bearer token). Setup guide: https://api.wave.co/mcp.
Known tools 2
search_docsSearch Wave's public developer documentation: the developer portal, OpenAPI specification, versioning policy, product overview, and contact pages.
Inferred read-onlyread_docRead one public Wave document in full, by the `uri` (or short slug) returned by search_docs or resources/list.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.wave-docs]
url = "https://wave.co/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"wave-docs": {
"type": "http",
"url": "https://wave.co/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: wave-docs
Remote MCP URL: https://wave.co/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"wave-docs": {
"url": "https://wave.co/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"wave-docs": {
"type": "http",
"url": "https://wave.co/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "wave-docs",
"transport": "streamable-http",
"url": "https://wave.co/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.