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

[Agents, API & MCP](https://openemail.uk/features.md#agents)

# 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://openemail.uk/mail/inbox) [Get Started](https://openemail.uk/signup.md)[All features](https://openemail.uk/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.

54

tools, fewer if your role holds less

2

transports: Streamable HTTP and SSE

0

keys to paste

How it works

## Your role decides the tool list

A tool you may not use is never listed, so a viewer’s client has no send tool at all. Your role is 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 OpenEmail to sign in.

## Approve it first, remove it later

You see what is asking and where your access would go before anything is granted. Account → Connected apps lists what holds a token and removes it.

## Tools a client can call

Only those your role allows 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.openemail.uk/sse

```
{  "mcpServers": {    "openemail": {      "url": "https://api.openemail.uk/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 your role and the permission it lacks.

More than mail

Templates, rules, contacts and tracking have tools too.

Good practice

## Getting the most out of it

1. 01
   
   Connect what you trust
   
   A client’s token reaches the whole mailbox, not a part of it.
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.

Where it stands

## Good to know

Questions

## Asked often

Keep going

## Works well with

OAuth for third-party clients

Soon

Self-service client registration with PKCE, so an app can ask for access properly.

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 OpenEmail and read it in a mailbox built around it. The free plan covers one domain.

[Open mail](https://openemail.uk/mail/inbox) [Get Started](https://openemail.uk/signup.md)[Read the reference](https://openemail.uk/docs/knowledge/agents/mcp.md)