Overview

Interactive setup

For Claude Code, Cursor, Codex, and OpenClaw, run one command. It detects your clients and writes the Rilo configuration:

npx rilogtm connect

Open or restart the configured client. Clients with remote MCP OAuth support open Rilo's browser sign-in when they connect. If your installed client does not, use the API-token fallback in its guide.

Using claude.ai / Claude Desktop? Paste the Rilo URL in Claude's connector settings and complete browser sign-in. See the Claude Desktop guide for the exact click path. ChatGPT support is not production-verified.

The endpoint is the same everywhere:

https://growth-mcp.getrilo.ai/mcp

Verify the connection

Do not stop at a green connector badge. Run a safe Rilo tool call:

Show my Rilo workspace overview.

You are connected when Rilo returns your workspace overview. Then connect LinkedIn from Setup when you are ready for search and outreach.

API tokens for headless access

CI, servers, and environments without a browser can use a personal API token (gtm_…). Create one from the clearly labeled API tokens section in Setup and send it as an Authorization header:

{
  "mcpServers": {
    "rilo": {
      "url": "https://growth-mcp.getrilo.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Interactive users do not need an API token. Treat a token like a password, store it in a secret manager, and revoke it if it leaks.

Troubleshooting

• Browser sign-in does not open. Copy the sign-in URL printed by the CLI into a browser on the same machine.
• 401 or "unauthorized" in a headless setup. The API token is missing, mistyped, or revoked. Create a replacement in Setup.
• Tools don't show up. The config is usually stale. Remove the old rilo entry, add it again, and restart the client.
• Connection refused or 404. Check the endpoint - it must end in /mcp:

https://growth-mcp.getrilo.ai/mcp

After the connection check passes, your agent is ready for real work. You can watch its actions in your workspace.