Connect

Every client needs the same URL:

https://api.poc.app.waylovoice.ai/mcp

The steps below sign in as you. The first time the client connects, your browser opens the Waylo dashboard. Sign in if asked, check the agent and organization on the consent screen, and click Allow. See Authorization.

For a server or a job with no person present, connect with an API key instead.

Claude CodeCopy Anchor Link

claude mcp add --transport http waylo https://api.poc.app.waylovoice.ai/mcp

Add --scope user to use it in every project, or --scope project to share it with your team in .mcp.json.

Then run /mcp in Claude Code, choose waylo and sign in.

Claude Desktop and claude.aiCopy Anchor Link

1. Open Settings → Connectors and click Add custom connector.
2. Enter a name, like Waylo Voice, and the URL above.
3. Click Connect and sign in.

CursorCopy Anchor Link

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "waylo": {
      "type": "http",
      "url": "https://api.poc.app.waylovoice.ai/mcp"
    }
  }
}

Open Cursor's MCP settings and sign in to waylo.

Cursor registers itself when it connects, so Waylo can't confirm who runs it and the consent screen shows Unverified app. That's expected: allow it if you started the connection from Cursor.

With an API keyCopy Anchor Link

Send an API key in the Authorization header. There is no sign-in: the agent acts as the key and sees only the tools its scopes allow.

After you create or rotate a key, the dashboard shows the Claude Code command with the key filled in:

claude mcp add --transport http waylo https://api.poc.app.waylovoice.ai/mcp --header "Authorization: Bearer sk_waylo_..."

In Cursor, add headers to the server in mcp.json:

{
  "mcpServers": {
    "waylo": {
      "type": "http",
      "url": "https://api.poc.app.waylovoice.ai/mcp",
      "headers": { "Authorization": "Bearer ${WAYLO_API_KEY}" }
    }
  }
}

Set WAYLO_API_KEY in the environment Cursor runs in, so the key stays out of the file.

Other clientsCopy Anchor Link

Any MCP client works if it supports:

• the Streamable HTTP transport;
• MCP authorization (OAuth 2.1 with PKCE), to sign in as a person. The client finds the sign-in itself from the server's 401 response. It must be a public client: Waylo issues no client secrets.
• or a custom Authorization header, to use an API key.

Check the connectionCopy Anchor Link

Signed in as a person, ask the agent "Who am I in Waylo?". It calls getCurrentUser and answers with your name, email and role.

With an API key, ask it to list the Waylo tools it has. They should match the key's scopes. A key with only Catalogs: Write, for example, has listCatalogs, getCatalog, createCatalog, updateCatalog, listCatalogItems and createCatalogItems, plus listPresets and getProviderCatalog, which any key gets. Any other tool answers Unknown tool.