notmuchproxy
Enables LLMs to search and read email from a notmuch archive, providing tools for searching threads, retrieving messages, and listing tags through an MCP endpoint.
README
notmuchproxy
Give an LLM read-only access to your email.
notmuchproxy is a small API server over a notmuch email archive. It exposes the same four tools two ways:
- an OpenAPI/REST API (schema at
/openapi.json), usable as an Open WebUI tool server - an MCP endpoint (streamable HTTP at
/mcp/), usable from Claude Code, claude.ai, and any other MCP client
There is no UI and no write path: the server only ever reads the archive, so the worst an over-eager LLM can do is search your email too enthusiastically.
The tools
| Tool | REST endpoint | Description |
|---|---|---|
search_email |
GET /search?q=... |
Search threads with notmuch query syntax (from:, to:, subject:, tag:, date:, free text) |
get_thread |
GET /threads/{thread_id} |
Every message in a thread, oldest first, bodies as plain text |
get_message |
GET /messages/{message_id} |
A single message by Message-ID |
list_tags |
GET /tags |
All tags in the archive |
Plus an unauthenticated GET /healthz. Everything else requires
Authorization: Bearer $NOTMUCHPROXY_API_KEY — including the MCP endpoint.
The MCP tools are derived from the OpenAPI schema at startup, so the two
surfaces can't drift apart.
Configuration
Everything is environment variables:
| Variable | Required | Description |
|---|---|---|
NOTMUCH_DATABASE |
yes¹ | path to the notmuch database root (the directory containing .notmuch); the docker image defaults it to /mail |
NOTMUCHPROXY_NOTMUCH_BIN |
no | notmuch executable (default: notmuch) |
NOTMUCHPROXY_EXCLUDE_TAGS |
no | comma-separated tags (e.g. spam,deleted) whose messages are excluded from all results — searches (even explicit tag:spam queries), threads, single messages, and the tag list. Useful for noise and for keeping adversarial spam content away from the model. |
NOTMUCHPROXY_CORS_ORIGINS |
no | comma-separated origins allowed for CORS; * (the default) allows any origin, empty string disables CORS. Needed when a browser calls the API directly, e.g. tool servers added in Open WebUI's user settings. The auth token remains the actual access control. |
Authentication
Pick exactly one mechanism (the server refuses to start with both or neither); it applies to both the REST API and the MCP endpoint.
Static bearer token — simplest; what Open WebUI's OpenAPI tool servers and
Claude Code's --header flag speak. claude.ai custom connectors can not use
this mode (they only support OAuth).
| Variable | Description |
|---|---|
NOTMUCHPROXY_API_KEY |
the bearer token clients must present |
OIDC via an external identity provider — works with any OIDC IdP (authentik, Keycloak, Google, ...). notmuchproxy presents a spec-compliant MCP authorization server to clients — including the dynamic client registration claude.ai requires — while acting as an ordinary OIDC client of your IdP upstream (your IdP does not need to support DCR itself). Tokens issued through the flow are accepted on both the MCP and REST endpoints.
| Variable | Description |
|---|---|
NOTMUCHPROXY_OIDC_CONFIG_URL |
the IdP's OIDC discovery URL, e.g. https://auth.example.com/application/o/notmuchproxy/.well-known/openid-configuration for authentik |
NOTMUCHPROXY_OIDC_CLIENT_ID |
client id of the app registered at the IdP |
NOTMUCHPROXY_OIDC_CLIENT_SECRET |
client secret of that app |
NOTMUCHPROXY_PUBLIC_URL |
public base URL of this server, e.g. https://notmuch.example.com — used for OAuth callbacks and discovery metadata; claude.ai requires HTTPS |
IdP setup (authentik example): create an OAuth2/OpenID provider with a
confidential client and redirect URI $NOTMUCHPROXY_PUBLIC_URL/auth/callback,
scopes openid profile email. Who may authorize is controlled by your IdP's
own policies (in authentik, bind the application to users/groups).
¹ optional if the host has a notmuch config that already points at the database.
Running in production
The server is distributed as a docker image. Mount your maildir — which must
already contain the .notmuch index — read-only at /mail:
docker run -d -p 8000:8000 \
-e NOTMUCHPROXY_API_KEY=some-long-random-string \
-v /path/to/your/mail:/mail:ro \
ghcr.io/igor47/notmuchproxy:latest
Indexing (notmuch new) is not done by this container — keep running it
wherever your mail is delivered. The container picks up index updates
automatically since xapian readers don't block writers.
docker compose, as a non-root user
The image runs as a built-in non-root user (uid 1000) by default. If your
maildir is owned by a different user, override user: so the container can
read the mount — no rebuild needed:
services:
notmuchproxy:
image: ghcr.io/igor47/notmuchproxy:latest
restart: unless-stopped
# run as the uid/gid that owns your maildir (`id -u`/`id -g`);
# omit entirely if uid 1000 can read your mail
user: "1000:1000"
ports:
- "8000:8000"
environment:
NOTMUCHPROXY_API_KEY: ${NOTMUCHPROXY_API_KEY:?set this in .env}
volumes:
- /path/to/your/mail:/mail:ro
The app never writes to the archive (and the :ro mount enforces that), so
read permission on the maildir is all it needs.
Connecting clients
Open WebUI
In static mode, add an OpenAPI tool server (Admin Settings → Tools):
- URL:
http://your-host:8000 - Auth: Bearer, key = your
NOTMUCHPROXY_API_KEY
Open WebUI fetches /openapi.json (which is unauthenticated, like /healthz)
to discover the tools, then sends the bearer token on each call.
In OIDC mode, use Open WebUI's MCP tool server type instead, pointed at
https://your-host/mcp with OAuth 2.1 auth — it performs the same discovery
and login flow as claude.ai.
Tool servers added under Admin Settings are called from the Open WebUI
backend, but ones added in a user's own Settings → Tools are called directly
from the browser — that path needs CORS, which is enabled for all origins by
default (lock it down with NOTMUCHPROXY_CORS_ORIGINS=https://your-webui-host).
claude.ai (OIDC mode only)
Settings → Connectors → Add custom connector, URL https://your-host/mcp.
Claude discovers the OAuth endpoints, registers itself dynamically, and sends
you through your IdP's login/consent in the browser. No client id/secret needs
to be entered on the claude.ai side.
Claude Code
Static mode:
claude mcp add --transport http notmuch http://your-host:8000/mcp \
--header "Authorization: Bearer $NOTMUCHPROXY_API_KEY"
OIDC mode — omit the header; Claude Code runs the OAuth flow in your browser:
claude mcp add --transport http notmuch https://your-host/mcp
Other MCP clients
Any client that speaks streamable HTTP can connect to http://your-host:8000/mcp,
authenticating with the static bearer token or the OAuth flow depending on
the server's configured mode.
Development
Tooling is managed by mise; the notmuch CLI must be on your PATH (it's in every distro's repos).
mise install # python + uv
mise run install # create venv, sync deps
mise run test # run the test suite (builds a throwaway notmuch archive)
mise run check # ruff lint + format check + pyright (CI mode)
mise run check:fix # same, but auto-fix what's fixable
mise run dev # serve on :8000 against generated fixtures (key: dev-key)
Other tasks: mise run fixtures (regenerate the local dev archive),
mise run docker:build, mise run docker:test (run the suite inside docker),
mise run docker:run. See mise tasks for the full list.
CI runs the same mise tasks, then runs the suite again inside the docker image
(against Debian's notmuch rather than the host's) before pushing to
ghcr.io/igor47/notmuchproxy on pushes to main and v* tags.
Architecture notes
- notmuch access: shells out to the
notmuchCLI using--format=jsonoutput, via a thin wrapper insrc/notmuchproxy/notmuch.py. No Python bindings, so there is no libnotmuch version-matching to worry about; the database path is passed via theNOTMUCH_DATABASEenvironment variable. - one definition, two protocols: the FastAPI routes are the source of
truth; fastmcp's
FastMCP.from_fastapi()converts the OpenAPI schema into MCP tools at startup and dispatches tool calls to the routes in-process. - bodies:
text/plainparts are preferred; HTML-only messages get a naive tag-stripped rendering. Attachments are listed by filename but not served. - fixtures:
python -m notmuchproxy.fixtures <dir>generates a small synthetic maildir + notmuch index, used by the tests andmise run dev.
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.