---
title: "Email MCP server"
description: "Connect Claude or any MCP client to your Nextmail mailbox. It reads, searches, sends and labels mail as you, once you sign in and approve it."
url: "https://nextmail.sh/features/mcp"
---

[AI & agents](https://nextmail.sh/agents/features.md#connect)

# MCP server Your mailbox, in the AI client you already use.

Claude, or any MCP client, can read, search, send and label your mail through your own account. Connecting one takes a sign-in, not a key.

[Open mail](https://nextmail.sh/mail/inbox) [Get Started](https://nextmail.sh/signup.md)[Agent features](https://nextmail.sh/agents/features.md)

In short

## What is an MCP server?

The Model Context Protocol lets an AI client call tools that another service offers. The client reads the server’s tool list and picks what fits your request.

501

tools, fewer if your role or your approval gives less

2

transports: Streamable HTTP and SSE

0

keys to paste

How it works

## Your role and your approval decide the tool list

A tool that your role or this client’s access does not cover is never listed, so a read-only client has no send tool at all. Both are checked again on every call.

## Sign in instead of pasting a key

Give the client the endpoint. It finds the authorization server, registers itself and sends you to Nextmail to sign in.

## Choose what it gets, change it later

Before anything is granted you see what is asking and where your access would go, and choose its workspace, addresses and permissions. Account → Connected apps changes that or removes it.

## Tools a client can call

Only those your role and your approval allow are listed.

listThreads Search threads with operators getThread A thread’s newest message sendEmail Send from an address you name modifyLabels Add or remove labels whoAmI What your role allows

## Point a client at it

The endpoint is all a client needs.

Clients still on SSE use https://api.nextmail.sh/sse

```
{  "mcpServers": {    "nextmail": {      "url": "https://api.nextmail.sh/mcp"    }  }}
```

What you get

## In the product today

Acts as you

No service account, and no wider access than your own.

Refusals say why

A refused call names the permission, and whether your role or the client’s access lacks it.

More than mail

Templates, rules, contacts and tracking have tools too.

Good practice

## Getting the most out of it

1. 01
   
   Give it the least it needs
   
   Start from Read only and add what the client needs. You can change it in Connected apps: less access applies on its next call, and anything new once it reconnects or reloads its tools.
2. 02
   
   Name the sender
   
   There is no default address, so a send that names none is refused.
3. 03
   
   Ask whoAmI first
   
   A missing tool is more often a permission you lack than a missing feature. whoAmI lists yours.

Questions

## Asked often

Keep going

## Works well with

OAuth for third-party clients

Apps register themselves and sign in with PKCE, and you choose the workspace, addresses and permissions each one gets.

REST API

A documented HTTP API with issuable, scopable, revocable keys.

Ask your inbox

A chat that can act, not just answer. On every plan, Free included.

Start

## Your domain, your mail.

Point a domain at Nextmail and read it in a mailbox built around it. The free plan covers one domain.

[Open mail](https://nextmail.sh/mail/inbox) [Get Started](https://nextmail.sh/signup.md)[Read the reference](https://nextmail.sh/docs/knowledge/developers/mcp.md)