Connect your inbox
For a team member who's been handed their own inbox. Five minutes, no account needed.
Your administrator created an inbox for you and gave you credentials. You can read and send mail from it two ways — point an AI agent at it, or use a normal mail app. Either way, you only ever see your own inbox; you can't reach a teammate's mail, and they can't reach yours.
What you were given
Depending on how you'll use it, your admin sent you one or both of these:
| Credential | Looks like | For |
|---|---|---|
| Your email address | [email protected] | Both paths |
| An inbox key | ak_1a2b3c… | Connecting an AI agent (MCP / CLI) |
| An IMAP password | abc123… | Connecting a normal mail app |
If you're missing the one you need, ask your administrator — these are shown only once when the inbox is created, so they may need to reissue them.
Option A — Connect an AI agent (MCP)
Works with Claude Desktop, Cursor, Windsurf, Cline, and any other MCP-compatible client. Add a server block to your client's config and paste your ak_ key as MYAGENTMAIL_KEY. Claude Desktop example (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"myagentmail": {
"command": "npx",
"args": ["-y", "myagentmail-mcp"],
"env": { "MYAGENTMAIL_KEY": "ak_your_inbox_key" }
}
}
}
Cursor (~/.cursor/mcp.json) and Windsurf (~/.codeium/windsurf/mcp_config.json) use the exact same block. Restart the client and the email tools appear — your agent can now read your messages, reply in-thread, and draft mail, all scoped to your inbox.
Use the ak_ key you were given — not a tk_ key. The ak_ key is locked to your inbox alone; a tk_ key would expose the whole team's mail.
Option B — Command line
For scripts or a terminal-based agent loop, the CLI is lighter than the MCP server:
export MYAGENTMAIL_KEY=ak_your_inbox_key
npx myagentmail-cli messages list # your inbox only
npx myagentmail-cli messages list --direction inbound # just what came in
Option C — A normal mail app
Prefer Apple Mail, Outlook, or Thunderbird? Add an account with these IMAP/SMTP settings, using your email address as the username and the IMAP password you were given:
| Server | Port | Security | |
|---|---|---|---|
| Incoming (IMAP) | imap.myagentmail.com | 993 | SSL/TLS |
| Outgoing (SMTP) | smtp.myagentmail.com | 587 | STARTTLS |
Username: your full address (e.g. [email protected]). Password: your IMAP password. That's it — your mail app syncs the inbox like any other account.
What you can and can't do
Your key and credentials are scoped to one inbox. You can read, send, reply, and draft from your inbox. You cannot list or open anyone else's inbox, and you can't create new inboxes or change billing — those stay with your administrator.
Lost your key, or think it leaked? Tell your administrator — they regenerate it for your inbox in one click (dashboard → your inbox → Agent API key → Regenerate key). Your address, mail history, and IMAP access are untouched; only the old key stops working. See API keys & scopes for the security model.