Quickstart
Cursor
One command writes Rilo into Cursor's MCP configuration.
Recommended: one command
npx rilogtm connect
Detects Cursor and writes the MCP config. The CLI does not complete sign-in; if your Cursor version supports remote MCP OAuth, Cursor prompts when it connects.
Verify the connection
Open Cursor's agent panel and ask:
Show my Rilo workspace overview.
You are connected when Rilo returns your workspace overview. If Cursor never offers browser sign-in, use the API-token fallback below.
Headless fallback
Machines without a browser can use a personal API token. Create one from the
API tokens section in Setup and add it to
~/.cursor/mcp.json:
Add to ~/.cursor/mcp.json (replace YOUR_TOKEN)
{
"mcpServers": {
"rilo": {
"url": "https://growth-mcp.getrilo.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Store the token in a secret manager. Rotate or revoke it from Setup.
Troubleshooting
- Browser sign-in does not open - copy the sign-in URL printed by the CLI into a browser on the same machine.
- 401 in a headless setup - the token is mistyped or revoked. Create a
replacement in Setup and update
mcp.json. - Tools don't show up - remove the old
riloentry frommcp.json, add it again, and restart Cursor.