AI Phone Call API & MCP Server
Give your code, and your agent, a phone line and a team.
Everything LumisReach does is reachable three ways: a REST API, a hosted MCP server your AI agent plugs straight into, and Lincoln AI, the agent that takes a whole job in plain language and runs it. One key works on all three, and you can create it yourself today.
- REST API
- 90+ endpoints, v1
- MCP server
- 37 tools, Streamable HTTP
- Lincoln AI
- 110+ tools, via API or MCP
- Auth
- one bearer key, optional scopes
- Access
- self-serve in Settings
- AI phone calls
- AI text conversations
- Email, iMessage, Slack
- Numbers with agents
- Transcripts and recordings
- Signed webhooks
- Lincoln AI
- Tenant isolation
What one key opens
- 90+REST endpoints on v1Calls, texts, numbers, history, billing
- 37MCP toolsClaude, Cursor or any MCP client
- 110+Tools Lincoln runs for youCampaigns, contacts, video, knowledge
- $0To read your dataHistory, config and billing reads are free
The parts you don't have to build
Reaching a real person by phone is mostly plumbing: carriers, registrations, retries, transcripts, billing. Here is what each piece costs you to build, and what it looks like instead.
- Building it yourselfWith LumisReach
- First AI callBuy a number, stand up SIP and media, wire a voice model, handle retries and voicemailPOST a phone number and a goal. The agent calls, retries if nobody answers, and reports back
- TextingRegister a brand and a 10DLC campaign, then wait weeks before a message deliversRegistered shared senders, so the first AI text goes out as approved traffic today
- Inbound lineProvision a number, build an answering agent, then bolt on transfers and bookingOne request buys the number and configures the AI that answers its calls and texts
- Other channelsA mail provider, an Apple device for iMessage, and a bot per chat appQuick Email, Quick iMessage and Slack or Discord posts on the same key
- The recordStore audio, run transcription, write summaries, stitch it all to a contactTranscripts, AI summaries, recordings, texts and emails per person, free to read
- EventsPoll for call state and diff it yourselfHMAC-signed call and SMS webhooks, with the full transcript on call.ended
- Multi-step workYour own agent loop, planning and approval UI over dozens of APIsHand the whole task to Lincoln AI; it plans, runs the tools and asks before it spends
From key to first call in minutes
No sales call, no number to buy, no brand registration before the first conversation. Quick calls and texts go out from LumisReach's shared senders, so an agent can reach someone as soon as the key exists.
Connect the MCP server →- 01
Create a key
Settings, then Developer API, in the app. The key is shown once and works across the whole v1 API and every MCP tool. Add a card under Billing for anything that costs money.
- 02
Connect your agent, or your code
Point Claude, Cursor or any MCP client at mcp.lumisreach.com/mcp with the key as a bearer header. Or call api.lumisreach.com/api/v1 directly; every MCP tool is a thin wrapper over the same endpoint.
- 03
Make the first call
Send a number and a goal to start_ai_phone_call (or POST /v1/quick/ai-calls), then poll the job for per-destination status, the outcome and a summary of what was said.
- 04
Hand over whole jobs
When the task is bigger than one call, message Lincoln AI. It builds the campaign, imports the contacts, sets up the number, and stops for your approval before anything that costs money.
- 05
Grow into your own numbers
When people need to call you back, or volume outgrows the shared pool, buy your own number with its agent attached and subscribe to signed webhooks for every call and text.
An MCP session, start to finish
- You
Call Dana at +1 415 555 0123 and find out if she still wants the quote. Try twice if she doesn't pick up.
- Claude
start_ai_phone_call { goal, to_numbers: ["+14155550123"], retry_attempts: 1 }
- Claude
get_quick_action_status → completed, goal_achieved
- Agent
Dana picked up on the second try. She still wants the quote and asked for it by Friday.
- You
Great. Ask Lincoln to put everyone who hasn't replied to last week's quote into a follow-up text campaign.
- Claude
ask_lincoln → awaiting_approval: send_text_message to 14 contacts, $0.05 per message
The tool calls are what the agent sends on its own. The call, its recording and transcript, and the contact all land in your LumisReach workspace like any other conversation.
What the surface actually covers
The same platform the dashboard runs on, not a preview shim. Each area is available as REST endpoints and, for the ones an agent needs, as MCP tools.
Quick Agent Actions
An AI phone call toward a goal with automatic retries and voicemail, an AI text thread that keeps answering replies, or a single text sent exactly as written. No number of your own required. Poll or cancel any job.
Email, iMessage and chat
Send a Quick Email to up to 20 people with no sending domain, a Quick iMessage from a shared Apple line, or post to a Slack or Discord channel you connect by webhook URL.
Numbers and their agents
Search, buy, configure and release numbers. Read and change everything on a number's answer page: voice, prompt, greeting, SMS auto-reply, knowledge, qualifying questions, booking, transfers, forwarding and the keypad menu.
Conversation history
Everyone you've called, texted or emailed, with per-channel counts. Speaker-labelled transcripts, AI summaries and tags per call, whole SMS threads, email history, and the raw recording audio. All free reads.
Lincoln AI
The agent behind Dashboard, Conversations. Send it a task and it runs outreach campaigns, contacts and segments, email marketing, automations, bookings, knowledge, lead generation, social accounts and AI video. Threads show up in the dashboard too.
Webhooks and primitives
Signed call.started and call.ended events with the full transcript, inbound SMS webhooks, plus direct dial, hangup and send-SMS endpoints for teams that already run their own agent on our numbers.
Caller trust
Branded caller ID and CNAM display names, brand and enterprise registration with LOA generation and signing, and reputation monitoring per number, so your calls arrive labelled instead of flagged.
Billing, usage and tenancy
Wallet, plan allowances, usage by category and itemized billing events to meter your own customers. Sub-entities give each customer an isolated workspace and a key you can revoke on its own.
The rules the surface keeps
Nothing spends without a yes
Lincoln stops and returns awaiting_approval before buying a number, placing a call, sending texts or publishing a video. Your code or your agent answers every pending approval explicitly.
Scopes and isolation are server-side
Keys can be restricted to scopes like voice:read or lincoln:write, in the style of Stripe restricted keys. A sub-entity key cannot read a sibling or its parent's private data, and MCP tools inherit exactly the same checks.
Built for retries
Every write accepts an Idempotency-Key, errors share one envelope with per-field detail, lists use the same cursor pagination, and keys are hashed at rest.
Asked before signing
01Do I need to talk to sales to get a key?
No. Create one under Settings, then Developer API. A key made there is unrestricted, so it works on the whole v1 API and every MCP tool, including Quick Agent Actions and Lincoln AI.
Reading data is free. Anything that places a call, sends a message or buys a number draws on your wallet, so add a card under Billing first.
02Should I use the API, the MCP server, or Lincoln?
Use the REST API when your product decides exactly what happens: a button that places a call, a backend that meters usage. Use the MCP server when an AI agent is doing the deciding and needs phone, text and history as tools.
Use Lincoln when the task is a whole job rather than one step, like building a campaign or setting up a number end to end. It is reachable from both the API and MCP, so they combine freely.
03What does it cost?
A Quick AI phone call is $0.20 per call placed plus $0.20 per minute. A quick AI text is $0.05 per outbound message, and replies are free. An AI phone number is $5 per month, with its calls and texts at your plan's rates. Chat posts and every read are free.
Messaging Lincoln is free; the actions it takes bill exactly as they do in the dashboard, and only after you approve them. Lincoln comes with the Growth Marketing Manager plan.
04Can I bring my own model and orchestration?
Yes. The primitives (direct dial, hangup, send SMS, webhooks, numbers and caller trust) are a telephony and trust layer underneath whatever agent you already run.
If you would rather not run the voice agent at all, Quick Agent Actions and number configuration give you ours, on the same key and the same bill.
05Where do calls come from, and what are the limits?
Quick calls and texts go out from LumisReach's shared numbers. Each shared number is capped per day (75 calls, 500 texts) to protect its reputation, and the pool spreads work across numbers that still have room.
Recipients see a LumisReach number and cannot call it back to reach you. When you need replies routed to you, or more volume than the pool allows, buy your own number with setup_ai_phone_number.
06How do I keep my customers separated?
Create a sub-entity per customer and issue that customer a sub-entity-scoped key. It sees only its own numbers, calls and contacts, and revoking it touches nothing else.
Caller-trust reads walk up to the parent registration, so a sub-entity inherits brand standing without inheriting access.
Keep reading
Make the first call today
Create a key under Settings, then Developer API, connect the MCP server or hit the REST API, and have an AI agent on the phone in minutes. Planning something bigger, or a platform with many tenants? Book a call and we'll scope it with you.