A server that can send an email may not be able to search an inbox or manage messages. This email MCP server setup guide walks through choosing the right connection, adding a local server to Claude Desktop, testing its tools, and connecting Volanea without confusing MCP credentials with SMTP credentials.
To connect an email MCP server, choose a provider and a server that exposes the actions you need, then add that server to an MCP-compatible client using its documented transport and credentials. For Gmail, configure OAuth access; for SMTP, use the provider’s submission settings; for inbox management, use a server with IMAP or Gmail API tools. Connect, inspect the available tools, and test each action with an account you control.
What an email MCP server does
The Model Context Protocol (MCP) lets an AI client discover and call tools exposed by a server. An email server might expose sending alone, or also provide inbox search, message reading, drafting, and mailbox management. Those capabilities depend on the server’s tools and the account permissions it receives, not on Claude Desktop or another AI client by itself.
MCP clients discover available tools with tools/list. Under the 2026-07-28 specification, MCP is stateless: the earlier initialize/initialized handshake and Mcp-Session-Id header are removed. A server must implement server/discover to advertise its protocol versions, capabilities, and identity; clients may call it before another request or use it as a compatibility probe over STDIO.
For a real setup, the distinction is practical: the client connects to the server, discovers its tools, and only then can an AI agent call them. A send-only tool might accept a recipient, subject, and body. Inbox access requires additional tools, such as search and message retrieval. Treat these as examples of actions, not guaranteed tool names: the server’s tools/list response is authoritative and can vary with authorization.
Choose Gmail, SMTP, or a managed email service
Choose based on whether the agent is helping with a person’s mailbox or sending messages for an application. SMTP submits outgoing email. IMAP accesses and manages messages stored in mailboxes, including searching, fetching, and changing flags; it does not submit email. The IMAP4rev2 standard defines those mailbox actions separately from message submission.
| Option | Best fit | What it provides |
|---|---|---|
| Gmail API or Gmail-connected MCP server | Personal or team Gmail tasks | Gmail API access through OAuth; available actions depend on the connected server’s tools and permissions. |
| SMTP-backed MCP server | Sending from an application or provider account | Outgoing message submission; SMTP alone does not provide inbox search or reading. |
| IMAP-backed MCP server | Reading and managing a mailbox | Message and mailbox access, including search and flag changes; sending requires a separate submission method. |
| Volanea | Application email with campaigns and workflows | Transactional email, campaigns, and automations through one API, plus an MCP server with 23 tools on every plan. |
Gmail API access starts with enabling the API in a Google Cloud project, configuring the OAuth consent screen, and creating OAuth 2.0 client credentials for user access, as described in Google’s Gmail API quickstart. For SMTP, message submission normally uses port 587 with STARTTLS; port 465 is the default for implicit TLS. The hostname and login are provider-specific. For an application that needs receipts, password resets, campaigns, and workflows, a managed service is a better fit than routing product email through a personal inbox.
Prepare your email account and credentials
Before configuring a server, decide what it needs to do and prepare the corresponding access:
- Gmail API: Enable Gmail API access in a Google Cloud project, configure the OAuth consent screen, and create OAuth 2.0 client credentials. Use permissions appropriate to the actions you need; search and reading require mailbox access, while sending is a separate action.
- SMTP: Get the provider’s hostname, submission port, TLS mode, username, and password or token. SMTP submission commonly uses port 587 with STARTTLS or port 465 with implicit TLS. RFC 8314 recommends TLS 1.2 or later for mail submission.
- IMAP: Get the mailbox-access host, port, TLS mode, and credentials from the provider. IMAP commonly uses port 993 with implicit TLS; a client must authenticate and select a mailbox before working with its messages.
Keep credentials out of AI prompts, public repositories, screenshots, and configuration files shared with other people. Store secrets in a protected local environment or secret manager, and give an agent only the access needed for its task.
For Volanea SMTP relay, the username is volanea and the password is the project’s secret API key. The MCP server is a separate connection: it lives at https://api.volanea.com/mcp and takes a project API key as a bearer token (or OAuth sign-in), not an SMTP username and password. Start with the sk_test_ key while you set things up. The steps are in the next section.
Email MCP server setup in Claude Desktop
Claude Desktop supports local MCP servers. On macOS, its configuration file is ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows, it is %APPDATA%\Claude\claude_desktop_config.json. A local server entry uses an mcpServers object containing a command and an args array, as shown in the MCP local-server tutorial.
For a local email server, add an entry under mcpServers with the command and arguments from that server’s installation instructions, then restart Claude Desktop, open the tools area, and confirm the expected email actions appear.
Connect Volanea’s MCP server
Volanea’s MCP server is remote, so there is nothing to install. It runs at https://api.volanea.com/mcp over HTTP, on every plan including Free.
- Create a free Volanea account at app.volanea.com/signup and open your project.
- Copy the connect command from your project settings. It comes pre-filled with your
sk_test_key. Test-key sessions render and log email but never deliver it, which is what you want while an agent is wiring things up. - Add the server to your client. In Claude Code, run this inside your own project:
claude mcp add volanea --transport http https://api.volanea.com/mcp \
-H "Authorization: Bearer sk_test_..."
Cursor, Windsurf, and other MCP clients take the same two values in their mcpServers config: the URL and the Authorization header.
- Or use OAuth instead of a key. Clients that support MCP authorization (Claude connectors, Cursor, the MCP Inspector) can add the URL with no header. The client opens a browser, you sign in to Volanea, and you pick the project and test or live mode the agent may use:
claude mcp add volanea --transport http https://api.volanea.com/mcp
- Check the tools. Ask the agent to run
get_project_status. It returns your plan, reputation, and verified domains. You should also see tools such ascreate_template,create_workflow,send_test_email, andcheck_delivery. - Run a test send. Ask the agent to send a test email with
send_test_email, then read it back withcheck_delivery. MCP test sends always run in test mode, whichever key you used, so an agent can’t mail a real person. - Go live from your app, not the agent. Verify your sending domain (
setup_domainreturns the DNS records), then switch your app’s code to the live key. The code the agent writes into your app is what sends real email once you deploy it. Campaigns the agent creates are drafts that a human sends, and workflows start paused.
Under the current MCP protocol, clients can use server/discover to learn a server’s protocol version and capabilities, then call tools/list to obtain the tools available to them. A typical email tool set could include a send action and, for a mailbox-enabled server, search and message retrieval. Treat those descriptions as examples: rely on the actual list returned by your server rather than assuming a Gmail or SMTP connector uses particular tool names.
Send a test email and verify the connection
Test the action the agent will actually perform. A connected server may expose search or draft tools without exposing a send action, and a successful tool response does not by itself confirm delivery.
- Confirm the MCP server is connected and inspect the tools it returns.
- For a send test, confirm a sending action is available and send a plain-text message to an address you control.
- Check the destination inbox, including its spam folder, and review the provider’s response or logs if the message is missing.
- For inbox access, separately test a search and fetch a message you can safely inspect.
A Volanea project key beginning sk_test_ renders and logs messages but does not deliver them, and Volanea’s MCP test sends always run in test mode. To reach a real inbox, send from your app with a live key after verifying your domain. You don’t need to request Amazon SES production access for that. For more on authentication and delivery practices, see our email deliverability and sending guides.
Troubleshoot common email MCP setup problems
If Claude Desktop shows no tools, check that the local process launches with the configured command and arguments. With STDIO, the client launches the server as a subprocess, sends newline-delimited messages over standard input, and expects standard output to contain only MCP messages; diagnostic text on stdout can break the connection. If discovery succeeds but no actions appear, inspect the tool list and account authorization.
For Gmail, check that the Gmail API is enabled and that the OAuth consent screen and client credentials are configured. For SMTP connection errors, confirm the provider’s hostname, port, TLS mode, and authentication details. If reading works but sending fails, the server may expose IMAP access without a separate SMTP submission tool. A remote endpoint error is usually a mismatch between the server’s connection method and the client configuration, so use a client that supports the method supplied by that server.
When a Gmail MCP server is not enough
A Gmail connection suits an agent working with a person’s inbox. Product notifications, customer campaigns, and event-driven sequences need application email infrastructure instead. We combine transactional email, campaigns, and visual workflows through one API and send through Amazon SES. We also provide an AI email marketing workflow guide for teams planning campaign automation.
Our pricing page lists Free at $0 with 1,000 emails per month, unlimited contacts, one sending domain, and the MCP server’s 23 tools. Free messages include a small “Sent with Volanea” footer badge; paid plans remove it. The comparison-table list prices are Starter ($5) for 7,500 emails, Growth ($20) for 50,000, and Scale ($149) for 200,000. Annual billing works out to Starter at $48 ÷ 12 = $4/month, Growth at $192 ÷ 12 = $16/month, and Scale at $1,430.40 ÷ 12 = $119.20/month.
For example, an application sending 7,500 messages monthly and needing workflows can use the Starter volume, while a team sending 50,000 monthly can compare Growth; an app reaching 200,000 can consider Scale. Each email credit sends one email to one recipient, credits reset monthly without rollover, and sending pauses at the limit rather than accruing overage charges. If your need is a single Gmail inbox, use a Gmail MCP integration; if you need application delivery and campaigns alongside MCP tools, start free with 1,000 emails a month.
FAQ
How do I connect an email MCP server to Gmail?
Enable the Gmail API in a Google Cloud project, configure its OAuth consent screen, and create OAuth 2.0 client credentials. Then configure a Gmail-connected MCP server with the credentials and permissions it requires, connect that server to your MCP client, and inspect its tools. Gmail API search uses Gmail-style queries, but the server determines which actions the agent can call.
Can an MCP server send email through SMTP?
Yes. The MCP server needs to expose a sending tool that submits messages through an SMTP provider, and it needs that provider’s hostname, port, TLS mode, and authentication details. SMTP submission commonly uses port 587 with STARTTLS or port 465 with implicit TLS. SMTP does not provide inbox searching by itself.
Can an email MCP server read and manage messages as well as send them?
Yes, if it exposes mailbox tools and has suitable authorization. IMAP supports searching, fetching, and managing messages and mailboxes, while SMTP handles message submission. A combined server may expose both; check its tool list for the actions you need instead of assuming a send tool can read mail.
What happens when Volanea’s monthly email credits run out?
Sending pauses until the next billing month or an upgrade; there is no overage billing. Credits reset at the start of each billing month and do not roll over. Contact storage is unlimited on every plan, so the monthly email volume—not the number of stored contacts—is the relevant limit when estimating fit.