Yodu AI Employees MCP

npx add-mcp 'https://app.yodu.ai/api/mcp'

Configure Claude Desktop, Claude Code, Cursor, or another Streamable HTTP client for Yodu Platform MCP.

Every client needs the same endpoint and authorization header:

URL: https://app.yodu.ai/api/mcp
Authorization: Bearer YOUR_YODU_API_KEY

Claude Code

claude mcp add --transport http yodu https://app.yodu.ai/api/mcp \
  --header "Authorization: Bearer YOUR_YODU_API_KEY"

After adding the server, list MCP servers and ask Claude Code to list Yodu's tools. Begin with get_workspace.

Claude Desktop

Add this entry to claude_desktop_config.json:

{
    "mcpServers": {
        "yodu": {
            "url": "https://app.yodu.ai/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_YODU_API_KEY"
            }
        }
    }
}

Restart the client after changing its configuration.

Cursor

Add the same server object to ~/.cursor/mcp.json or use Cursor's MCP settings interface:

{
    "mcpServers": {
        "yodu": {
            "url": "https://app.yodu.ai/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_YODU_API_KEY"
            }
        }
    }
}

Codex

Add a remote server to your Codex configuration:

[mcp_servers.yodu]
url = "https://app.yodu.ai/api/mcp"
bearer_token_env_var = "YODU_API_KEY"

Set YODU_API_KEY in the environment that launches Codex, using a key from Settings → MCP & API. Keep its value out of committed files. Restart the client and begin with get_workspace to confirm the connected workspace. See the official Codex MCP documentation for configuration details.

This connection operates Yodu tools; it does not provide model access to Yodu employees. Configure a supported subscription or provider separately in Yodu's model settings.

Other clients

The client must support MCP over Streamable HTTP and custom request headers. Configure a stateless HTTP server at the Yodu endpoint and send the bearer header on every request.

Connection checklist

• The endpoint ends in /api/mcp, not /api/docs.
• The transport is HTTP, not a local stdio command.
• The header begins with the exact Bearer scheme.
• The key has not been revoked and belongs to the intended workspace.
• A corporate proxy allows HTTPS requests and does not strip the authorization header.
• The first successful tool call is read-only and confirms the workspace identity.

If the server appears connected but tools fail, use Errors and troubleshooting.

[

Platform MCP tools

Complete reference for the 58 tools exposed by Yodu's workspace-scoped Platform MCP server.

](https://docs.yodu.ai/developers/platform-mcp-tools)[

Scopes and security

Understand Yodu API key scopes, role checks, secret handling, and deliberate public-platform exclusions.

](https://docs.yodu.ai/developers/scopes-and-security)