Maexry MCP Server

Maexry includes a built-in Model Context Protocol (MCP) server that lets AI assistants — Claude, OpenAI, Gemini, and any MCP-compatible agent — read and act on your email directly. No cloud relay. No third-party intermediary. The server runs entirely on your device.

What It Is

MCP is an open protocol that lets AI agents call tools in external applications. Maexry implements a Streamable HTTP MCP server that exposes your inbox as a structured tool surface. When you connect an AI assistant to Maexry via MCP, it can search your email, read threads, classify messages, draft replies, manage action cards, and write Sovereign Vault notes — all within the privacy boundaries you have already configured.

Every MCP tool call is subject to the same rules as the app itself: PII redaction runs before any content reaches your AI provider, write operations are scoped to your authenticated accounts, and nothing transits Maexry's servers.

Who It Is For

• Claude Code, Claude Desktop users who want their AI assistant to act on email context
• OpenAI Assistants / GPT users building agents that need inbox access
• Gemini CLI users automating email workflows
• Power users who write custom scripts or automation pipelines against their inbox

How It Works

When Maexry is running and your vault is unlocked, the MCP server starts automatically on 127.0.0.1 at a fixed local port. It accepts connections only from localhost — external hosts cannot reach it.

Each connection requires a Bearer token generated inside Maexry. Tokens are scoped to your device and expire when you lock your vault or quit the app.

| Property | Value | |---|---| | Transport | Streamable HTTP | | Host | 127.0.0.1 (localhost only) | | Protocol Version | 2025-06-18 | | Authentication | Bearer token (per-session) | | Auto-start | Yes — after vault unlock | | Auto-stop | Yes — on vault lock or app quit |

Multi-Account Support

If you have multiple Gmail accounts in Maexry, each account is accessible via MCP. The config dialog lets you select which accounts the MCP server exposes. Most tools accept an optional account_id parameter to target a specific account. If omitted, the tool operates on your primary account.

What the Server Can Do

The MCP server provides 25 tools across five capability groups:

| Group | Tools | Operations | |---|---|---| | Core read | 7 | Fetch emails, threads, categories, action cards, daily brief, vault notes | | Core write | 9 | Classify, snooze, draft, archive, delete, mark, star, save notes | | Label & move | 3 | Add/remove Gmail labels, move to folder, list labels | | Batch operations | 4 | Archive, delete, mark read, label — up to 50 messages per call | | Attachments | 2 | List and download email attachments |

See the MCP Tools Reference for full parameter and return documentation.

Privacy Guarantees

The MCP server inherits all of Maexry's privacy architecture:

• PII redaction applies — the on-device Sentry engine scrubs sensitive data before any content reaches your AI provider
• Localhost-only binding — 127.0.0.1 means no external network access is possible
• Bearer token required — no unauthenticated access; tokens are session-scoped
• Per-account scoping — tools cannot access accounts you have not explicitly exposed in the config dialog
• Write operations are logged — archive, delete, and classify actions are recorded in the local database

Your AI assistant gains access to your inbox structure — it does not gain access to your encryption keys, your master password, or your AI provider credentials.

Getting Started

See the MCP Setup Guide to enable the server and connect your first AI assistant.