01
Follow up on invoices
Send reminders from a dedicated accounts address, watch the reply thread, and escalate disputes or billing changes to a person.
OpenClaw integration
Connect Sentvia through MCP and give OpenClaw a dedicated address it can send from, monitor, search, and reply through—without connecting your personal inbox.
The short answer
Verified July 2026
Sentvia connects to OpenClaw as a local MCP server. Install sentvia-mcp, add an API key, and OpenClaw discovers 21 tools for inboxes, messages, threads, drafts, domains, webhooks, and address rules.
Setup
Paste this instruction into OpenClaw. It will fetch the agent-ready install guide and ask for the API key only when it needs one.
Recommended setup
Set up SentVia email for yourself: fetch <https://docs.sentvia.ai/agent-install.md>
and follow it. Ask me for the API key when you need it.Register the public MCP package, add one environment variable, and probe the server directly.
Create a Sentvia API key in the dashboard. OpenClaw uses it to access only the inboxes and mail in that Sentvia workspace.
SENTVIA_API_KEY=sv_live_…Add sentvia-mcp to OpenClaw’s managed MCP registry. The package runs locally over stdio wherever OpenClaw runs.
openclaw mcp add sentvia --command npx --arg -y --arg sentvia-mcpAdd the API key to the server environment, then open a live connection and confirm that OpenClaw can discover the tools.
openclaw mcp doctor --probeExpected result: OpenClaw reports the sentvia server as connected and exposes 21 tools.
Native email tools
The MCP server exposes the same email primitives as the Sentvia API. OpenClaw chooses the tool; Sentvia handles inbox identity, mail delivery, storage, and threading.
View all MCP tools →3 tools
Create, list, and delete dedicated addresses
5 tools
Send, reply, forward, read, and search
2 tools
List conversations and retrieve full threads
3 tools
Create, review, and send drafts
2 tools
Add and inspect sending domains
3 tools
Create, list, and delete inbound event hooks
3 tools
Add, list, and delete allow/block rules
A useful first run
“Create an inbox called ‘claw’, email me an introduction, then check the inbox for replies.”
OpenClaw calls create_inbox, receives a live Sentvia address, sends with send_message, then uses search_messages or list_threads for the return path.
Put the inbox to work
Start with a narrow job where email is already the system people use to coordinate and respond.
01
Send reminders from a dedicated accounts address, watch the reply thread, and escalate disputes or billing changes to a person.
02
Email vendors or service providers, keep the back-and-forth in one thread, and return confirmed details to the scheduling workflow.
03
Classify new requests, prepare or send routine replies, and forward uncertain cases with the original conversation attached.
04
Receive receipts, verification messages, newsletters, and service notifications somewhere separate from personal email.
Operate deliberately
Keep the agent inbox separate from credentials-bearing accounts, start with a narrow allowlist, limit tools to the job, and require draft review for sensitive or irreversible messages. Sentvia enforces address rules and suppression server-side, but the agent still needs explicit permissions and escalation rules.
Yes. OpenClaw can register the sentvia-mcp package as a third-party MCP server and discover its tools through OpenClaw’s managed MCP registry.
No. Sentvia provisions a dedicated programmatic inbox for the agent. Use a provider-specific integration when the agent must operate inside an existing human mailbox.
The simplest OpenClaw pattern is scheduled polling with search_messages or list_threads. For push workflows, use Sentvia webhooks or the realtime WebSocket through an endpoint the agent can consume.
Yes. The MCP server includes draft tools, so a workflow can create a draft and require human approval before calling the send tool.
It is a thin local stdio wrapper over the Sentvia REST API and runs wherever OpenClaw runs. It requires Node 20 or newer and a Sentvia API key.
Start with 5 inboxes and 5,000 emails free, then scale when the workflow proves useful.