mcp server.md
The Wajo MCP server
Wajo exposes its platform to AI clients through a hosted MCP (Model Context Protocol) server. Any MCP-capable client — Claude Code, Claude.ai and Claude Desktop, Cursor, ChatGPT, VS Code, and others — can connect and drive the Wajo runtime end-to-end.
Endpoint and transport
- Endpoint:
https://mcp.api.wajo.ai/mcp - Transport: Streamable HTTP.
The server is stateless across connections, so it scales horizontally — you do not need sticky sessions.
Authentication
Two ways to authenticate, depending on your client:
- API key. Developer tools (Claude Code, Cursor, VS Code) send a Wajo API key (prefixed
wak_), either as anX-API-Keyheader or as a standardAuthorization: Bearer <key>. For example, in Claude Code:
claude mcp add --transport http wajo https://mcp.api.wajo.ai/mcp \
--header "X-API-Key: wak_..."
- OAuth. Consumer apps that cannot paste a key — Claude.ai custom connectors and ChatGPT developer-mode apps — use the MCP authorization (OAuth) flow. Add
https://mcp.api.wajo.ai/mcpas a custom connector and complete the sign-in prompt.
Every request is scoped to the authenticated user: you only ever see and touch your own agents, connectors, and sessions.
Searching the docs without an account
This documentation is itself searchable over MCP with no account and no authentication: connect to https://mcp.api.wajo.ai/mcp and call search_documentation. It is the one tool you can use before you authenticate — everything else on the endpoint is scoped to your account and prompts you to sign in the first time you call it.