Mailgent for Claude
Give Claude a real inbox and identity. Add the Mailgent MCP server and Claude gets mail, vault, 2FA, calendar, and payment tools — scope-gated to the agent's key.
Claude speaks MCP natively, so adding Mailgent is a config change, not an integration project. Drop the server into your MCP settings with an agent's key and the full Mailgent toolset shows up in the conversation.
From there Claude can send and read email, store and fetch secrets, generate TOTP codes, manage a calendar, sign with its identity, and pay per call — all gated by the scopes on the key you provide.
Connect in one config block
Add Mailgent to Claude Desktop's MCP server config (or any MCP client) with the agent's API key. The tools appear immediately, namespaced under mailgent.
Run it locally with npx, or point at the hosted endpoint at api.mailgent.dev/mcp.
{ "mcpServers": { "mailgent": {
"command": "npx",
"args": ["-y", "@mailgent-dev/mcp"],
"env": { "LOOMAL_API_KEY": "mgnt-..." } } } }What Claude can do
Once connected, Claude can triage an inbox and reply in-thread, pull a credential from the vault, clear a 2FA gate with a generated code, book a calendar event, sign a request to prove identity, or pay an x402-priced URL — each only if the key's scopes allow it.
FAQ
Does this work in Claude Desktop and the API?
Any MCP-capable Claude surface works. Add the server to the client's MCP config with the agent's key.
How do I limit what Claude can do?
Scope the agent's key. Tools outside the granted scopes don't appear or are rejected.
Give your agent an inbox.
A real email address, a vault, 2FA, and an identity in one API call.