Documentation

Connect an AI assistant

Renggo includes an MCP server, so Claude, Cursor or any MCP client can design, validate and publish flows in conversation.

Endpoint

The server is part of the Renggo API at /mcp, over Streamable HTTP, authenticated with a bearer key. Settings, then MCP shows your exact endpoint with a copy button.

https://YOUR-RENGGO-API/mcp

Create a key

In Settings, then MCP, generate a key. The secret is shown once. Grant only the scopes the client needs, and start read-only.

ScopeAllows
flows:readRead agents, flows, versions and the node schema
flows:writeCreate and modify draft flows
flows:publishPublish and roll back. This changes what live callers hear
kb:readList knowledge bases and search them
kb:writeCreate knowledge bases and add documents
analytics:readRead per-version call statistics

Connect your client

Claude Code sends custom headers natively:

Claude Code
claude mcp add --transport http renggo https://YOUR-RENGGO-API/mcp --header "Authorization: Bearer sk-YOUR-KEY"

Cursor reads ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

mcp.json
{
  "mcpServers": {
    "renggo": {
      "url": "https://YOUR-RENGGO-API/mcp",
      "headers": {
        "Authorization": "Bearer sk-YOUR-KEY"
      }
    }
  }
}

Claude Desktop's connector screen only accepts OAuth, so bridge it with the mcp-remote proxy in claude_desktop_config.json. Keep the space inside the environment variable, not around the colon in --header.

claude_desktop_config.json
{
  "mcpServers": {
    "renggo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://YOUR-RENGGO-API/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer sk-YOUR-KEY"
      }
    }
  }
}

Check it works

Ask your client to run whoami. It reports your organisation and the scopes you granted. If it does, everything else will work.

What to expect

  • Drafts save even when they're invalid. Only publishing requires a clean validation.
  • Publishing and rolling back are the only actions that change what live callers hear. Use a key without flows:publish if you want a person to do that step.
  • Knowledge base documents are processed in the background; a flow that references an empty base carries a warning.
  • The same key works without MCP: every tool is also available over plain HTTP under /api/v1/tools.