# The email API your agent can run.

URL: https://samva.dev/solutions/ai-agents

Point your agent at `mcp.samva.dev` or the `samva` CLI. It sends email, reads the replies, verifies your domain, and edits templates, and you publish the version you reviewed.

[Start sending free](https://samva.dev/signup)

[Read the docs](https://samva.dev/docs/developers/mcp)

## The email API your agent wires up for you.

Hand your agent a short brief. It reads the credential guide, connects over MCP or the samva CLI, sends an email, and reads the reply that comes back.

Connect an assistant to the hosted MCP server with an authorized account.

An agent sends an email and reads replies in its conversation.

## Email APIs were built for a human at a keyboard.

- **Setup by dashboard**: Domain records, senders, and webhooks mean clicking through screens your agent can't see.
- **Keys pasted into chat**: The agent needs a key, so someone copies a secret into a prompt.
- **Send-only**: The agent sends an email and never sees the reply.

## Read auth.md. Connect MCP. Send.

1. **Your agent reads auth.md.** Your agent reads /auth.md and the quickstart, and learns how to get a key.
   
   Authorize an agent with scoped access to your account.
2. **Connect the hosted MCP.** Add mcp.samva.dev to any MCP client that supports OAuth, or run samva login. A person approves the first credential.
   
   Configure the hosted Samva MCP endpoint in your assistant.
3. **Send and read.** The agent sends email and reads the conversation it starts. Replies reach your webhook as message.received.
   
   An agent calls sending and conversation tools to send email and read replies.

## What your agent can do.

An agent you run in your own MCP client or the CLI, using an API key you create, can:

Without a key, the server still answers questions about Samva and searches the template gallery.

- Send and schedule email, in a thread or a new one
- Read delivery events and customer replies
- Add and verify domains and senders
- Edit a template in a shared workspace, show you the diff, and publish the version you approved
- Run, pause, and resume campaigns
- Read and reply from its own mailbox, with sends you can hold for approval
- Manage webhooks and check readiness and usage

## Samva for ChatGPT, Claude, Cursor, and Grok

Open the Samva plugin in ChatGPT, connect one organization, and start with a read-only readiness check.

[Get notified about Claude, Cursor, and Grok](https://samva.dev/contact?subject=connectors)

- **Claude**: Claude logo
   
   Coming soon
- **ChatGPT**: [Open in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6a8ebcc4c4c48191b5a3a53638f7b972)
- **Cursor**: Cursor logo
   
   Coming soon
- **Grok**: Grok logo
   
   Coming soon

## Your agent gets an address.

Fig 9. Isometric drawing: an agent calls mailbox_reply through hosted MCP at mcp.samva.dev, the reply passes under a gate marked sendMode send whose lamp is lit, and it leaves the mailbox support@acme.samva.email on a rail to the customer, whose tape reads mailbox.message.received.

Fig 9.

Your agent connects to its mailbox through hosted MCP. Mail arrives as an event, the agent replies with a tool call, and the mailbox's grants and policies decide whether it sends or waits for a person.

## Build with your agent from here.

READ AUTH.MD

The machine-readable setup guide. Paste it into your agent.

- [Developers](https://samva.dev/developers): Typed SDK, REST, and the auth model. The same contract the agent uses.
- [Agent skills](https://samva.dev/docs/developers/agent-skills): Instructions that teach a coding agent which Samva surface to reach for.
- [MCP server](https://samva.dev/docs/developers/mcp): Connect any MCP client that supports OAuth and send email as tools.

## Questions from developers.

### Can my agent create its own key?

A person creates the first credential, through OAuth in an MCP client or samva login. After that, the agent can create and rotate keys through the API, within the access its own credential holds. Every key belongs to one organization.

### Which MCP clients work?

Any client that supports OAuth. Point it at mcp.samva.dev. The server also accepts an API key as a bearer header.

### What can the MCP server do?

Sending, replies, delivery events, domains and senders, templates, campaigns, scheduled email, webhooks, usage, and mailboxes. The MCP docs list every tool.

### Can my agent have its own inbox?

Yes. Create a mailbox on your samva.email subdomain or a domain you verified, and give the agent a mailbox-scoped key. The agent reads and replies through the API, the CLI, or hosted MCP, and you can hold its sends until a person approves them.

### How do I limit what an agent can send?

Give the agent a restricted API key that holds only the resources its job needs, such as sending email without managing domains, and revoke it at any time. Every key belongs to one organization, and its sends run under that organization's spend and daily limits.

## Hand your own agent the setup.

[Read the MCP docs](https://samva.dev/docs/developers/mcp)