Navrik
Sign Up

MCP server

Navrik exposes its capabilities to AI clients via the Model Context Protocol at /api/mcp.

  • Transport: Streamable HTTP — one POST per JSON-RPC message.
  • Auth: Bearer an sk_live_ API key (same keys as REST).
  • Tool surface: the tools are the lib/* service layer — the same operations the REST routes wrap. So an MCP client can read/write CRM, commerce, calendar, etc., within the key's workspace.
  • MCP vs REST: REST is for programmatic integration; MCP is for AI agents/assistants that discover and call tools. Same data, same workspace scoping.

Connecting a client

Point an MCP-capable client (e.g. Claude Code / Desktop) at https://www.navrik.co.uk/api/mcp with an Authorization: Bearer sk_live_… header. The client lists available tools and calls them over JSON-RPC.

OAuth connectors (Claude.ai, ChatGPT): these clients keep one connector per URL, and each connector is bound to one Navrik workspace at consent. To connect several workspaces, add one connector per workspace using its own URL, https://www.navrik.co.uk/api/mcp/w/<workspace-slug>. That URL is pinned to the workspace: consent skips the picker, and a token for another workspace is refused there.