Skip to main content

Rilo MCP

Connect your AI tools to Rilo using the Model Context Protocol (MCP) through Cequence AI Gateway. Rilo is go-to-market (GTM) infrastructure for AI agents: it lets an agent find leads, qualify them, build outbound sequences, and send on LinkedIn as you, while Rilo handles provider integrations, storage, scheduling, and safety limits.

Overview​

Rilo MCP is a remote, vendor-hosted MCP server. Rilo hosts and maintains the server, so no local installation is required.

  • Server URL: https://growth-mcp.getrilo.ai/mcp
  • Transport: HTTP (Streamable HTTP)
  • Hosted by: Rilo

The subjective judgment — who to target and what to say — stays with your agent. Rilo acts as the hands: it executes the mechanical work of search, sequencing, and sending.

Supported authentication types​

TypeSupportedNotes
Browser sign-in (OAuth-style)YesRecommended. Sign in to Rilo (via Google) and approve access in the browser when your client prompts for authentication.
API tokenYesFallback for headless clients, CI, or servers without a browser. Generate a personal token (gtm_…) from the API tokens section of Rilo Setup and send it as an Authorization: Bearer header.

Interactive users generally don't need an API token — use browser sign-in unless your environment can't complete an interactive OAuth flow.

What can you do with this MCP server​

Rilo exposes roughly 50 tools across seven areas:

  • Search & enrichment — Find leads and enrich them with additional profile and company data.
  • Sequences — Build and manage multi-step outbound sequences.
  • LinkedIn actions — Send connection requests, messages, and other LinkedIn actions on your behalf.
  • Inbox — Read and manage replies in your LinkedIn inbox.
  • Learning — Capture signals that help Rilo and your agent improve targeting and messaging over time.
  • Connect — Manage the connection between your agent, Rilo, and your LinkedIn account.
  • Observability — Inspect workspace status and monitor what your agent has done.

Every tool call returns the same response envelope, regardless of which area it belongs to:

{
  "ok": true,
  "data": {},
  "summary": "…",
  "signals": [],
  "learnings": []
}

summary describes what happened in one line, and signals flags anything unusual worth your agent's attention.

Prerequisites​

Before adding Rilo MCP in Cequence AI Gateway, ensure you have:

  • Access to Cequence AI Gateway at aigateway.cequence.ai
  • A Rilo account (sign up or sign in with Google at growth.getrilo.ai)
  • A LinkedIn account connected to Rilo from Rilo Setup — required before LinkedIn search or outreach tools will work
  • For headless/API-token authentication, a personal API token generated under Setup > API tokens in Rilo

Example workflows​

  • "Show my Rilo workspace overview."
  • "Find 20 leads matching my ICP and start a sequence."
  • "Show replies in my LinkedIn inbox from this week."
  • "Pause the sequence targeting VP of Engineering leads."
  • "Summarize what my agent sent on LinkedIn yesterday."

Connecting MCP server from Cequence AI Gateway​

  1. Log in to Cequence AI Gateway.
  2. Choose your tenant.
  3. Go to App catalogue.
  4. Filter by Remote MCP server.
  5. Search for Rilo and then select it.
  6. Select Create MCP server.
  7. Choose browser sign-in and complete the Rilo sign-in and approval flow, or provide an API token if you need headless authentication.
  8. Complete the remaining setup, select tools, and deploy.

Use the generated MCP server URL in your client as described in the Client Configuration docs. For detailed gateway setup steps and screenshots, see Create a third-party MCP Server.

Additional information​

  • Connect LinkedIn first: Search, sequence, and outreach tools depend on a LinkedIn account connected from Rilo Setup. Connect it before relying on your agent for outbound workflows.
  • API-token security: Treat an API token like a password — store it in a secret manager and revoke it immediately from Setup if it leaks.
  • Verification: Confirm the connection by asking the agent to show your Rilo workspace overview rather than trusting a green connector badge alone.
  • Troubleshooting: If tools don't show up, remove the existing rilo entry from your client config, re-add it, and restart the client. A 401/"unauthorized" response in a headless setup usually means the API token is missing, mistyped, or revoked. Confirm the endpoint ends in /mcp if you see a connection-refused or 404 error.
  • Official documentation: Rilo docs.
Last updated on