Hermes Agent + ripdr
Build an outbound agent around your own playbook.
Choose the research sources, qualification rules, and tools that fit your sales process. Connect Hermes Agent to ripdr through MCP, then combine phone outreach with your email provider and external LinkedIn workflow. Your agent coordinates the work; ripdr executes the scheduled phone touches.
Scale API access · Your connected tools · Your approved playbook
Best for technical founders and operators who want a configurable agent environment and explicit control over outbound execution.
Connect outreach as a tool the agent can use
Nous Research’s Hermes Agent supports remote MCP servers with configurable headers and tool filters. Add ripdr as a server, verify access to your contact groups and saved recordings, and expose only the tools your workflow requires. Start with read access to inspect the account, then grant outreach access when the playbook is ready to run.
Turn a repeatable playbook into a durable workflow
Define the qualification criteria, approved message library, channel spacing, and escalation rules outside any single chat. Track each contact’s enrollment and provider identifiers in durable state so a restarted agent can reconcile progress before taking another action. Use ripdr’s documented retry and idempotency behavior for supported REST outreach operations rather than assuming a repeated request is harmless.
Let each service do the work it owns
Hermes can orchestrate research and provider calls; ripdr schedules voicemail and missed-call steps after activation. Instantly can execute email steps with your connected account. Your integration should collect replies and callback events into a shared contact state, then coordinate suppression and handoff across services. This design keeps the workflow understandable when a provider is unavailable or a prospect responds early.
Five channels. Clear responsibilities.
| Channel | Execution | How it fits |
|---|---|---|
| Ringless voicemail | ripdr | Saved or previously generated recordings, sent through campaigns, sequences, or individual drops. |
| Missed calls | ripdr | A separate outreach touch that leaves a missed call without a voicemail recording. |
| Connected provider | Supported sequence email steps use your own Instantly account. Other providers can be coordinated externally. | |
| External workflow | Agent-prepared messages and authorized external execution or human tasks; no native ripdr LinkedIn sender. | |
| SMS | Eligible ripdr accounts | Optional on enabled Scale accounts with the required contact consent. Opt-outs always block sending. |
These are coordinated workflows, not a promise of a single native connector for every channel. Provider access, account permissions, and response handling must be configured before launch.
Connect Hermes Agent to ripdr
In Hermes, configure a remote MCP server using the url and headers fields documented by Nous Research. Set the URL to https://ripdr.com/api/mcp and provide Authorization: Bearer followed by your ripdr API key through your private configuration. Verify with list_groups and list_recordings before creating a sequence. Use Hermes tool filters to narrow exposure, while keeping ripdr key scopes as the account-side access boundary.
Open the integration hub for connection details and the tool catalog. The API and MCP guide covers supported operations and email sequence behavior.
Platform reference: Nous Research: Hermes MCP configuration. This is an independent ripdr workflow guide; third-party names do not imply endorsement.
Give your agent a concrete brief
Build a reusable outbound playbook for this approved CRM group. Inspect ripdr’s available tools and our provider connections first. Create a draft sequence with email, a saved voicemail recording, and a missed-call follow-up. Track contact IDs, enrollment state, and provider IDs durably. Check suppression before actions and reconcile uncertain results before retrying. Show me the plan before activation. Report replies, callbacks, delivery outcomes, and exceptions separately.
Adapt this example to your audience, permissions, and connected providers.
Frequently asked questions
Which Hermes does this guide cover?
This page covers Hermes Agent from Nous Research, specifically its documented MCP support. It does not refer to other products or models with the Hermes name.
Does Hermes need a local ripdr MCP package?
No. ripdr hosts a remote Streamable HTTP MCP server. Configure the server URL and Bearer authentication in Hermes. You still need a ripdr Scale account, the appropriate key scopes, and credits for outreach.
Will stopping Hermes stop my ripdr sequence?
No. Activated ripdr sequences run on ripdr’s servers. Pause the sequence explicitly when needed; shutting down the agent is not a pause command. External channel coordination may stop if your orchestrator is offline.
Put the plan to work
Give your next sequence a voice.
Prepare your contacts and recordings in ripdr, connect your agent, and build an outbound workflow around conversations worth having.
Ringless voicemail doesn't reach every number every time — carriers and voicemail systems vary. Each drop attempt uses 1 credit when dispatched. Learn more