Give your agent live email tools. Keep identity, scope, and confirmation explicit.
Use one remote Model Context Protocol endpoint for contacts, templates, flows, messages, analytics, and controlled actions across compatible clients.
✓OAuth for human operators; scoped first-party API keys for agent principals.
Tools with product meaning
Operator prompt
Inspect the onboarding flow, explain where contacts stop, and show the evidence before proposing a change.
Discover
email_* tools
Inspect
Company context
Propose
Controlled write
[ 01 / 03 ]Product tools
Expose operations, not a generic database connection.
Inspect with product meaning
Read contacts, message timelines, flow runs, suppressions, and metrics through purpose-built operations.
Create valid product objects
Render template versions, define segments, and assemble paused flows through validated schemas.
Refuse beyond authority
The credential's principal, ranked scope, and can-approve grant determine access—not the MCP client carrying it.
[ 02 / 03 ]Connect
Start MCP with a task you can verify.
Add one remote endpoint, authorize a real principal in the browser, and verify the returned tools with a read-only request.
The client discovers OAuth and the email_* tool surface from the same endpoint.
https://sendandretain.com/api/mcp[ 03 / 03 ]Related
Build around MCP clients
MCP
Connect an agent through OAuth or an API key and give it controlled access to the same capabilities as the product.
AI
See how scoped credentials, confirmations, and product checks constrain every connected client.
Flows
Inspect and prepare event-triggered flows through the same tools the product uses.
Questions people ask us
Connect your agent to one controlled email surface.
Add the endpoint, authenticate the principal, and verify the boundary with a read-first task.