MCP server

The WAVE MCP server lets an MCP-capable client — Claude Desktop, Cursor, or your own agent — call WAVE through the Model Context Protocol. It is the people-facing companion to WAVE's machine discovery surfaces.

Two surfaces, one protocol

  • MCP guide (this page) — how a person wires WAVE into their MCP client.
  • MCP endpoint — the machine descriptor an agent reads at /.well-known/mcp on any WAVE surface.

Install

The server is published as @wave-av/mcp-server (open source).

npx @wave-av/mcp-server

Configure your client

Add WAVE to your MCP client config, supplying your API key as an environment variable:

{
  "mcpServers": {
    "wave": {
      "command": "npx",
      "args": ["@wave-av/mcp-server"],
      "env": { "WAVE_API_KEY": "wave_sk_live_…" }
    }
  }
}

Get a key from the developer portal. Access is enforced server-side at the gateway — the key scopes what the tools can do.

What you get

The server exposes WAVE capabilities as MCP tools, so an assistant can call the same API you would through the SDK. The authoritative, versioned tool list lives in the @wave-av/mcp-server README — see also the Agent Developer Kit.

For agents

Autonomous agents don't need this page — they read the machine descriptor directly:

  • MCP descriptor: /.well-known/mcp
  • x402 discovery: /.well-known/x402
  • Agent skill: /skill.md · Capability index: /llms.txt
Agent commerce isn't a separate product — every WAVE capability is callable by people and payable by agents over HTTP-402 (x402).