MCP servers
The public MCP server, with no sign-in, and the workspace's, signed in as a person.
Wavo Intelligence runs two MCP servers, split by sign-in: a public one any agent calls with no key, and the workspace's, which acts as the person signed in.
The public MCP server
The music industry's newest stories, the day's topics and Apple Music's US top ten. Every tool only reads, and answers what the public API answers, under the same schema.
| Property | Value |
|---|---|
| Address | https://terminal.cloud.wavo.me/mcp |
| Transport | Streamable HTTP |
| Sign-in | None |
| Server card | https://terminal.cloud.wavo.me/mcp/server-card |
| Rate limit | Tool calls: 60 requests a minute for each IP address, 30 of them at once, a bucket apart from the API's. Listing and the handshake spend nothing. |
Tools
| Tool | What it answers | Input |
|---|---|---|
list_stories | The newest stories | topic (optional): one of recorded, rights, live, platforms, capital, policy |
search_stories | Search the newest stories | query: string, 1–200 characters |
get_story | One story | id: string, 1–64 characters |
list_topics | The day's topics | None |
get_chart_top | Apple Music's US top ten | limit (optional): integer, 1–10 |
Connecting a client
Any client that speaks Streamable HTTP connects with the address alone. In Claude Code:
claude mcp add --transport http wavo-news https://terminal.cloud.wavo.me/mcpIn the page
Every page of the site hands the same tools to the browser's own agent through WebMCP (document.modelContext.registerTool()), by the same names and inputs. Each runs as a read of the public API on the page's origin, and spends the caller's API bucket.
The workspace's MCP server
Automations, tasks, Projects, mail, connected apps and data in your Wavo Intelligence workspace. Its tools act as the person signed in, and it is open to Wavo's team today: any account can sign in, and every tool refuses one outside it.
| Property | Value |
|---|---|
| Address | https://terminal.cloud.wavo.me/api/mcp |
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 with PKCE (S256), through WorkOS AuthKit |
| Protected-resource metadata | https://terminal.cloud.wavo.me/.well-known/oauth-protected-resource |
| Server card | https://terminal.cloud.wavo.me/api/mcp/server-card |
Signing in
- A request without a token is answered
401, withWWW-Authenticate: Bearernaming the protected-resource metadata, which names AuthKit. - The client registers with dynamic client registration, at
https://terminal.cloud.wavo.me/api/oauth/registeror the endpoint AuthKit's metadata names, or with a client ID metadata document. - The person signs in to Wavo Intelligence in a browser and lets the client in (the authorization code grant, with PKCE);
offline_accessasks for a refresh token. - The client calls with
Authorization: Bearer <access token>.
There are no API keys. /auth.md walks an agent through each step.
Connecting a client
claude mcp add --transport http wavo-intelligence https://terminal.cloud.wavo.me/api/mcpThe client opens the sign-in in a browser the first time.