rivomi
Get started

Claude-ready

Your pipeline, available to your agents

Everything the app can do, the API can do. A versioned REST API with an OpenAPI spec, and an MCP server so Claude can work your workspace directly.

Get an API keyRead the docsAPI reference

Two doors, one set of rules

Every MCP tool and every REST endpoint calls the same function behind the app, so they cannot answer differently, and a key can never do more than the person who made it.

  • MCP server

    30 tools for Claude, Cursor and any MCP host

  • REST + OpenAPI

    Versioned under /api/v1, documented

  • Sign in or use a key

    OAuth for hosted connectors, keys for scripts

  • Scoped to one workspace

    Revoke a key or an app at any time

$ claude mcp add rivomi

✓ connected · 30 tools

Claude · your workspace

Who replied this week, and what did they want?

list_enrollments → 6get_conversation × 6

Six replies. Three asked about pricing, two are already on a deal. Draft answers for the other four?

6

replies
this week

Connect in one line

In claude.ai or Claude Desktop, add a custom connector with the URL below and no key. It asks you to sign in and pick a workspace.

Claude Code
claude mcp add --transport http \
  --header "Authorization: Bearer $KEY" \
  rivomi https://rivomi.com/api/mcp
curl
curl "https://rivomi.com/api/v1/prospects?status=replied" \
  -H "Authorization: Bearer $KEY"

MCP endpoint: https://rivomi.com/api/mcp

Then just ask

Claude calls the tools. You get answers from your own workspace, not a summary of a dashboard.

“Who replied this week, and what did they say?”

“Show me the three-flame people from the competitor sources.”

“Approve the drafts in the Advisors queue that cite a comment.”

“Import this CSV into a new list and score it against our segment.”

Three scopes, and one thing no key can do

read

Prospects, lists, agents, runs and conversations. Any member can create it.

write

Change lists, agents and targeting; start imports and scoring runs, which spend credits.

send

Send invitations and messages from connected accounts. Only after a person has accepted the sending terms in the browser.

Scopes nest: send includes write, which includes read. Nothing can be sent until a person has accepted the LinkedIn sending terms in the browser. No key, token or tool can accept them for you.

DocsGuides for connecting Claude, Cursor and scripts, and a walkthrough of every tool.Read more API referenceEvery endpoint, its scope and the MCP tool that mirrors it, generated from the OpenAPI spec.Read more Account safetyThe same pacing and breakers apply to every send, whether it came from the app or the API.Read more

Point Claude at your pipeline.

Create a workspace, issue a key with the scopes you want, and ask who replied this week.

Get startedSchedule a call