Connecting AI Clients

Add your team's Wato MCP gateway to Claude Code, Codex, Cursor, or any remote MCP client.

Wato exposes your team's tools and memory through a remote MCP server. Connect any MCP-capable client and it can read memory, draft and submit memory changes, and call your team's approved tools through the same governed gateway.

Copy your exact config from the product

Open Teams → [Team] → Setup ("Use Wato MCP in your agent") to copy a pre-filled config for your team — it has tabs for Claude Code, Codex, Cursor, and Other clients. The examples below use the team slug engineering; replace it with your team's slug.

How connections are scoped

Server endpoint: https://mesh.watolabs.com/api/mcp (self-hosted and pilot workspaces use the domain Wato provides — replace mesh.watolabs.com accordingly).
Team scoping: either a ?team=<slug> query parameter (Claude Code, Cursor, most clients) or an x-mesh-team header (Codex). Use whichever your client's config below shows.
Server name: by convention wato-<team> (for example wato-engineering).
Auth: every client authenticates with OAuth.

Claude Code

Run this from the project where you use Claude Code:

claude mcp add --transport http wato-engineering "https://mesh.watolabs.com/api/mcp?team=engineering"

Run the command from the project where you use Claude Code.
Open Claude Code and run /mcp to authenticate the Wato server.
Once connected, Claude Code can call the Wato tools for this team.

Codex

Add this configuration to ~/.codex/config.toml:

[mcp_servers.wato-engineering]
url = "https://mesh.watolabs.com/api/mcp"
http_headers = { "x-mesh-team" = "engineering" }

Then log in:

codex mcp login wato-engineering

Merge the config into ~/.codex/config.toml (create the file if needed).
Run codex mcp login wato-engineering and complete OAuth.
Restart Codex or start a new session so the MCP tools load.
Call wato_get_usage_guide first when you want the current best-practice workflow.
Ask Codex to use Wato, or call mesh_search_tools to discover team-visible tools.

Codex scopes the team by header

Codex sends the team in the x-mesh-team header, so its url has no ?team= query parameter. The other clients put the team in the URL.

Cursor

Paste this into .cursor/mcp.json (or merge the server entry into an existing file):

{
  "mcpServers": {
    "wato-engineering": {
      "type": "http",
      "url": "https://mesh.watolabs.com/api/mcp?team=engineering"
    }
  }
}

Paste the JSON into .cursor/mcp.json or merge the server entry into an existing file.
Restart Cursor or reload MCP servers from Cursor settings.
Authenticate when Cursor prompts for the Wato MCP server.

Other clients

Use this endpoint in any MCP client that supports remote Streamable HTTP servers with OAuth:

https://mesh.watolabs.com/api/mcp?team=engineering

Create a remote HTTP MCP server entry in your client.
Use the endpoint above as the server URL.
Complete the OAuth flow when the client asks you to authenticate.

After connecting

Whatever the client, start a Wato session the same way:

Call wato_get_usage_guide for the current team, your memory permissions, and the recommended workflow.
Call mesh_search_tools to discover the tools visible to your team.

See the Reference for the full tool catalog.