Discover and configure the MultiMail MCP server through Glama's directory. Auto-generated configs, online testing, and gateway proxy.
Glama is an MCP server directory and gateway platform that indexes public MCP servers, generates configurations, and provides a web interface for testing tools. The MultiMail MCP server is listed on Glama, making it easy to discover, test, and configure for your preferred client.
Glama's standout feature is automatic configuration generation. Select MultiMail from the directory, choose your MCP client, and Glama produces the exact configuration block you need — complete with the correct file path, format, and structure for that specific client.
Glama also offers a gateway proxy that can route MCP requests through its infrastructure. This is useful for teams that want centralized MCP server management, logging, or need SSE transport without running a local server process.
Sign up at multimail.dev and create an API key from your dashboard. This key authenticates all MCP server requests.
Visit glama.ai/mcp/servers and search for 'MultiMail' or '@multimail/mcp-server'. The listing shows all available tools, descriptions, and configuration options.
On the MultiMail server page, select your MCP client from the dropdown. Glama generates the exact configuration block for your client, including the correct file path and format.
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
}
}
}Copy the generated config and paste it into your MCP client's configuration file at the path Glama indicates. Replace the placeholder API key with your actual MultiMail API key.
Open your MCP client and ask the AI to list your MultiMail mailboxes. You can also use Glama's online testing tool to verify the server is responding before configuring your local client.
| Tool | Description | Example |
|---|---|---|
| send_email | Send an email from your agent mailbox to any recipient. | Send an email after verifying the tool works in Glama's tester. |
| reply_email | Reply to a received email, maintaining the thread context. | Reply to a message using a config generated by Glama. |
| check_inbox | Check a mailbox for new or unread messages. | Test inbox checking in Glama before deploying to your client. |
| read_email | Read the full content of a specific email including headers and body. | Read an email through the gateway proxy for centralized logging. |
| create_mailbox | Create a new agent mailbox on your MultiMail account. | Create a mailbox from any Glama-configured client. |
| list_mailboxes | List all mailboxes on your MultiMail account. | List mailboxes to verify your API key works correctly. |
| get_thread | Retrieve an entire email thread to see the full conversation history. | Pull full thread history for an email conversation. |
| search_contacts | Search your contact list by name, email, or tags. | Search contacts using Glama's tool testing interface. |
| add_contact | Add a new contact to your MultiMail contact list. | Add a contact from any MCP client configured via Glama. |
| tag_email | Tag or categorize an email for organization and filtering. | Tag emails from any Glama-supported MCP client. |
| list_pending | List all emails currently awaiting human approval. | Check the approval queue from your preferred client. |
| decide_email | Approve or reject a pending email in the oversight queue. | Approve or reject pending emails from any connected client. |
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
}
}
}The base configuration Glama generates for most stdio clients.
{
"mcpServers": {
"multimail": {
"url": "https://glama.ai/mcp/proxy/@multimail/mcp-server",
"transport": "sse",
"headers": {
"x-api-key": "mm_live_your_key_here"
}
}
}
}Use Glama's gateway proxy for SSE transport.
1. Go to glama.ai/mcp/servers and find @multimail/mcp-server
2. Click 'Test' to open the interactive tool tester
3. Enter your API key when prompted
4. Try list_mailboxes or check_inbox to verify connectivity
5. Once confirmed, copy the generated config for your clientUse Glama's web interface to test MultiMail tools before configuring your client.
Glama auto-generates configs for:
- Cursor: ~/.cursor/mcp.json
- Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
- VS Code + Cline: cline_mcp_settings.json
- Zed: ~/.config/zed/settings.json (context_servers format)
- And many more...Glama generates configs tailored to each MCP client's format.
Glama's online tool tester lets you verify that MultiMail's MCP server works with your API key before touching any local config files. Test list_mailboxes first to confirm connectivity, then copy the generated config to your client.
If your MCP client only supports SSE (not stdio), Glama's gateway proxy can convert the connection. This lets you use MultiMail with SSE-only clients without running a local stdio-to-SSE bridge.
Different MCP clients use different config formats and file paths. Glama knows the exact format for each client and generates configuration you can paste directly. This eliminates guesswork, especially for clients like Zed that use non-standard config structures.
Bookmark the MultiMail listing on Glama (glama.ai/mcp/servers/@multimail/mcp-server) for quick access to config generation, tool documentation, and testing whenever you set up a new client or help a team member get started.
Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a 38-tool MCP server. Formally verified in Lean 4.