Built for AI agents
Ringless voicemail your AI agent can actually run
ripdr is no longer dashboard-only. Hosted MCP and a REST API let Cursor, Codex, Claude, and your own automations list contacts, launch campaigns, enroll sequences, and react to signed webhooks — so outreach flows stay in your stack instead of a brittle browser macro.
Why agents — not another UI wrapper
Sales teams already use AI for research, copy, and CRM updates. Ringless voicemail was the gap: most tools expect a human clicking Start. ripdr closes that loop with first-class agent surfaces — MCP tools named for outreach jobs, idempotent sends, and push webhooks when something actually happens on the phone.
Hosted MCP — no local package
ripdr runs MCP on ripdr.com. Add one URL + Bearer token in Cursor, Codex, Claude, or any Streamable HTTP client — your agent calls tools instead of clicking through the UI.
Outreach-shaped API, not a generic CRM dump
Endpoints match how reps actually work: list groups, pick a recording, create or start a campaign, enroll a sequence, send a single drop. Idempotency keys prevent double-sends.
Push events back to your stack
Signed outbound webhooks fire when voicemails deliver, prospects call back, or campaigns pause for credits — so agents and automations can update your CRM or alert a rep.
Agent-readable discovery
llms.txt, a JSON docs manifest, markdown articles, and OpenAPI give autonomous agents a clear map of what ripdr does and how to integrate safely.
Example agent workflow
Create an API key
Scale customers create an org-scoped key in Settings → Developer. Choose scopes for contacts, outreach, and account read.
Connect MCP or REST
Point your agent at the hosted MCP server or call /api/v1 directly. OpenAPI describes every request shape.
Prepare CRM + audio
Import contacts into a group in the dashboard (or create via API). Pick a recording storage_ref from your library.
Run outreach
Create a campaign, start it, or send one-off drops and missed-call touches. Server cron handles pacing after start.
React to webhooks
Subscribe to signed HTTPS webhooks for drop.delivered, inbound.callback, and campaign.paused — no polling required.
Full connection snippets, tool catalog, and REST paths live on the agent integration hub.
MCP + REST at a glance
- Hosted MCP —
/api/mcpwith Streamable HTTP; works in Cursor, Codex, Claude connectors, and any Bearer-capable MCP client. - REST API —
/api/v1with OpenAPI at /openapi.json. - Webhooks — HTTPS POST with
X-Ripdr-Signaturefor deliveries, callbacks, and campaign pause events. - Scale plan — API keys in Settings → Developer; sequences and full outreach via MCP require Scale.
Machine-readable discovery
Autonomous agents should start with these endpoints (also listed on the integrate hub):
- llms.txt — Plain-text agent discovery (start here)
- Docs manifest (JSON) — Full help corpus
- OpenAPI 3.1 — REST request schemas
- Hosted MCP — Streamable HTTP + Bearer auth
- REST base /api/v1 — Org API key required
- Developer guide — Auth, scopes, idempotency
FAQ
Can AI agents send ringless voicemail through ripdr?
Yes. Scale customers connect via hosted MCP (Cursor, Codex, Claude, and other MCP clients) or the REST API at /api/v1. Agents can list contacts, create campaigns, send single drops, enroll sequences, and read credit balance — without browser automation.
What is ripdr MCP?
ripdr hosts a Model Context Protocol server at ripdr.com/api/mcp. Authenticate with an org API key (Bearer ripdr_live_…) and your agent gets tools like list_groups, create_campaign, control_campaign, and send_drop. No npm package or local bridge required for HTTP-capable clients.
How is ripdr different from ringless tools without an API?
Most ringless platforms are dashboard-only. ripdr pairs ringless voicemail and missed-call outreach with a CRM, plus a public API, hosted MCP, OpenAPI spec, and signed webhooks — so AI agents and custom stacks can run outreach flows end to end.
Do I need to keep an agent connected while a campaign runs?
No. After you start a campaign or activate a sequence, ripdr's servers handle pacing and delivery. Use webhooks or poll get_campaign when you need status updates.
What plan do I need for the API and MCP?
The public API and hosted MCP require a Scale plan. Missed-call touches via API need Growth or Scale. Create API keys in Settings → Developer after upgrading.
How do agents discover ripdr capabilities?
Start with llms.txt for a plain-text map, then /api/docs/manifest for JSON help articles, /openapi.json for REST schemas, and /agents/integrate for connection snippets and endpoint tables.
Ready to wire your agent?
Copy MCP config, browse tools, and link to OpenAPI from the integration hub — or sign up and create your first API key on Scale.