Available for compatible assistants

Use the PureBox MCP Server from your AI assistant.

If your assistant supports Remote MCP using the Model Context Protocol, you can link it to your existing PureBox account and use the Hosted MCP Server for scans, suggestions, senders, History, and guarded cleanup plans. Your Gmail login and tokens stay inside PureBox, and you can unlink anytime.

What's live today

The PureBox MCP Server is live, with one important caveat.

Live now

The PureBox MCP server, protected-resource discovery, OAuth challenge flow, and Account revocation controls are live for compatible assistant clients.

Client support varies

Your assistant app must support adding a Hosted MCP Server through Remote MCP with OAuth. If it does not expose that setting yet, the PureBox MCP Server is ready but that app cannot connect yet.

The idea

Ask your assistant about your inbox, not the other way around.

You link PureBox once from inside a compatible assistant. After that, the assistant can ask PureBox about connection status, scan progress, suggestion counts, sender context, recent History, and server-owned cleanup plans. PureBox still enforces your account state, Gmail connection, plan limits, and safety checks.

Safe by design

The same control you already trust, extended carefully.

Guarded actions only

Assistants can use PureBox tools, but cleanup writes must go through PureBox-owned apply plans, idempotency keys, account checks, and the same limits your web account follows.

Your login is never shared

Assistants never see your Gmail tokens, your Google password, or any secret. PureBox keeps your Google connection to itself - the assistant only ever talks to PureBox.

You can unlink anytime

See every linked assistant and remove it in one tap from Account > Remote MCP (Model Context Protocol). Unlinking takes effect immediately.

No secret material leaves PureBox

Tools return only the scoped cleanup data needed for the task - never Gmail OAuth tokens, Supabase tokens, refresh tokens, passwords, or raw credentials.

How you'll use it

Three steps, and you stay in control of every one.

Connect a compatible client

Add the PureBox MCP Server as a Hosted MCP Server from an assistant or client that supports Remote MCP with OAuth, then sign in to your existing PureBox account.

Ask PureBox for context

Ask about scan status, reclaimable suggestions, sender patterns, or recent cleanup History. The assistant calls PureBox tools instead of guessing from a prompt.

Use guarded cleanup plans

When you ask to apply cleanup, PureBox prepares a bounded plan first. The apply step uses PureBox checks and status tracking, and you can still recover messages in Gmail.

Remote MCP access through the PureBox MCP Server follows the same rules as the rest of PureBox: review-first, reversible, and private.

See how we handle your data

Need help connecting?

Start with the connection guide. It explains the PureBox MCP Server URL, Hosted MCP Server requirements, starter prompts, and what to check when an assistant app does not expose Remote MCP settings yet.

Read the connection guide

For developers and integrators

PureBox MCP Server uses the Model Context Protocol.

PureBox exposes a secure Hosted MCP Server surface at POST /mcp for assistant platforms that support Remote MCP over OAuth. The production PureBox MCP Server resource is live at https://api.purebox.ai/mcp.

Transport: A single JSON-RPC endpoint over Streamable HTTP at POST /mcp. Standard MCP initialize, tools/list, and tools/call methods apply.
Authorization: OAuth 2.0 with resource-bound access tokens. Discover the protected resource at GET /.well-known/oauth-protected-resource; unauthorized calls return 401/403 with a WWW-Authenticate challenge. Tokens are scoped to the MCP resource and never carry Gmail OAuth scopes.
Compatible clients: PureBox accepts verified, resource-bound tokens from DCR-registered MCP clients. ChatGPT, Claude, Cursor, or other assistants can connect only when their client supports a Hosted MCP Server through Remote MCP with OAuth.
Current tool set: Tools include get_purebox_connection_status, start_purebox_scan, get_purebox_scan_status, get_purebox_suggestion_stats, list_purebox_suggestions, search_purebox_senders, get_purebox_sender_briefing, get_purebox_activity_summary, prepare_purebox_apply_plan, apply_purebox_apply_plan, get_purebox_apply_status, get_purebox_automation_candidates, enable_purebox_automation, and send_purebox_assistant_feedback.
The outcome envelope: Every tool result conforms to a shared shape: { outcome, data?, issue? }. outcome is one of ok, needs_user_action, blocked, or transient. Any non-ok result carries an issue with a machine code, a human title and detail, an imperative remediation string, and a cold-start-safe, token-free action_url (carrying ?source=assistant) the user can open to self-resolve.
Two layers, never crossed: Assistant-to-PureBox auth failures stay at the transport layer (401/403 + WWW-Authenticate). PureBox-to-Gmail state is reported only as non-secret data or a needs_user_action envelope inside a 200 - so a Gmail problem can never trigger an assistant re-link loop.
Connection management: Users list and revoke their own links from Account > Remote MCP (Model Context Protocol), backed by GET /v1/mcp/connections and POST /v1/mcp/connections/:id/revoke. Connection records expose only non-secret consent and audit metadata - never tokens or token hashes.

Status: the PureBox MCP Server protected resource is live. Connection success still depends on the assistant client supporting Remote MCP over OAuth and on the user having an existing PureBox account.