Why use MCP instead of the REST API
With the REST API, your code controls the flow: you call Sentvia, inspect the result, and tell the agent what happened. With MCP, the agent operates autonomously — Sentvia’s operations appear directly in the model’s tool list and the agent chooses when and how to use them.REST API
Your code orchestrates email. You decide when to send, receive, and search —
then pass results back to the agent.
MCP
The agent itself decides. It calls
send_message or search_messages directly
as part of its reasoning, with no intermediary code.Connect the MCP server
Point your MCP-capable client — Claude Desktop, or any MCP host — at the Sentvia server and authenticate with your API key:MCP config
The exact server command for your workspace is shown in the
dashboard. Authentication uses the same API keys as
the REST API — generate or manage keys under Settings → API Keys.
Available tools
The MCP server exposes the core Sentvia operations as discrete tools the agent can call:Inboxes
Create, list, and delete inboxes in your workspace.
Messages
Send, reply to, forward, retrieve, and search messages.
Threads
List threads and read full conversations.
Webhooks & Lists
Manage delivery endpoints and allow/block rules.
Every tool maps directly to an endpoint in the API reference.
Threading, idempotency, suppression, and attachments all behave identically whether
you call the REST API or invoke a tool through MCP.