What an agent can do in LumisReach
Place AI phone calls and text conversations, read call transcripts and recordings, and manage phone numbers.
Jobs on Rush that use LumisReach
- Call Every New Inbound Lead Within Minutes and Post the Outcome to Slack
- Chase Invoices More Than 30 Days Overdue by Phone and Log What Each Customer Said
- Confirm Tomorrow's Appointments by Phone Every Evening
How LumisReach connects
LumisReach is a remote MCP server, published by Lumis Laboratories, at https://mcp.lumisreach.com/mcp. It has no sign-in: you connect it with your LumisReach API key.
- Have a LumisReach account (lumisreach.com). Each person who connects LumisReach uses their own.
- Your LumisReach API key, starting lumisreach_. Create one in LumisReach under Settings > Developer API; calls and texts need a card under Settings > Billing.
- In the console, open Settings → Connections, press Connect on LumisReach, paste the key and press Add app. Rush lists the server's tools with the key before it saves it, so a key LumisReach refuses is never saved.
- Name
lumisreachin a run'sconnections, or switch it on in a Project, and the agent can use LumisReach's tools.
From Lumis Laboratories: LumisReach website · LumisReach's MCP documentation.
Connect it once in the console under Settings → Connections, pasting the key under its row, or from your server with POST /me/connections and the key in auth.
After that, a run that names lumisreach in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "LumisReach",
"url": "https://mcp.lumisreach.com/mcp",
"auth": {
"mode": "bearer",
"token": "<your key>"
}
}Put your key in auth.token: Your LumisReach API key, starting lumisreach_. Create one in LumisReach under Settings > Developer API; calls and texts need a card under Settings > Billing.
Whose LumisReach account the agent uses
Your LumisReach connection is personal: it belongs to the person who signed in. A run started in the console uses that person's LumisReach, and a run started with an API key uses the LumisReach of the member who created the key.
An agent made from a template for one of your app's users cannot hold a LumisReach connection: LumisReach connects with a person's own API key, which a template cannot carry.
More Communication integrations
Frequently asked questions
How do I connect LumisReach to Rush?
Open Settings → Connections in the console, connect LumisReach and paste your LumisReach API key, or send POST /me/connections with {"type":"mcp","name":"LumisReach","url":"https://mcp.lumisreach.com/mcp","auth":{"mode":"bearer","token":"<your key>"}} and your key as the token. Rush lists the server's tools with the key first: a key LumisReach refuses is 422 token_rejected, a good one is connected at once.
Does every run get my LumisReach account?
No. A run gets your LumisReach connection only when it names it in connections ("connections": ["lumisreach"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in LumisReach?
Place AI phone calls and text conversations, read call transcripts and recordings, and manage phone numbers. 3 published jobs use it; this page lists them.
Do I need a LumisReach account, and who pays for it?
Yes. LumisReach connects with an API key from your own LumisReach account, so each person who connects it brings their own account and key. Your LumisReach API key, starting lumisreach_. Create one in LumisReach under Settings > Developer API; calls and texts need a card under Settings > Billing. LumisReach bills what the agent does there to that account, at LumisReach's prices; Rush bills the run itself, its compute and models, as for any run.
Keep reading
- AI agents for operations teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to