Check readiness and scans
Ask whether PureBox is connected, start or resume a non-destructive scan, and check scan progress before cleanup is available.
get_purebox_connection_status, start_purebox_scan, get_purebox_scan_status
PureBox MCP server
Use PureBox from an AI assistant that supports remote MCP servers. Your assistant can ask PureBox about scans, suggestions, senders, History, and guarded cleanup plans while PureBox keeps your Gmail login and tokens private.
The PureBox server is ready, but your assistant app must support adding remote MCP servers with OAuth. If that setting is not available in your assistant, keep using the PureBox web app until your assistant client adds support.
PureBox treats MCP as a protected resource. Your assistant gets a resource-bound token for PureBox MCP, not your normal PureBox web session, not your Gmail OAuth token, and not your Google password.
Exact labels vary by assistant client. The safe sequence is the same: add the server, authorize PureBox, then ask for status before asking for cleanup.
Look for a connectors, integrations, tools, or MCP servers area. If your app does not expose remote MCP server settings, it cannot connect yet.
Use https://api.purebox.ai/mcp as the remote MCP server URL. Compatible clients can discover the protected resource and OAuth challenge automatically.
Complete the OAuth sign-in and consent flow with the Google identity already connected to PureBox. PureBox links existing accounts only.
Start with: "Ask PureBox for my connection status." If Gmail needs attention, your assistant should give you a safe PureBox link instead of retrying auth.
Ask whether PureBox is connected, start or resume a non-destructive scan, and check scan progress before cleanup is available.
get_purebox_connection_status, start_purebox_scan, get_purebox_scan_status
Ask for suggestion counts, a page of suggestions, sender context, or recent History so the assistant can brief you before action.
get_purebox_suggestion_stats, list_purebox_suggestions, search_purebox_senders, get_purebox_sender_briefing, get_purebox_activity_summary
Prepare and apply bounded cleanup plans, check apply status, review automation candidates, enable automation when your account allows it, and send feedback.
prepare_purebox_apply_plan, apply_purebox_apply_plan, get_purebox_apply_status, get_purebox_automation_candidates, enable_purebox_automation, send_purebox_assistant_feedback
Yes when the ChatGPT, Claude, or other assistant client you are using supports adding remote MCP servers with OAuth. If your app does not expose that setting yet, the PureBox MCP server is ready but that app cannot connect to it yet.
No. PureBox keeps Gmail OAuth tokens and Supabase tokens inside PureBox. The assistant receives a resource-bound MCP token for the PureBox MCP resource, not your Gmail credentials.
No assistant gets arbitrary Gmail access. Cleanup writes must go through PureBox-owned apply plans, idempotency keys, account checks, entitlement checks, and status tracking. Recovery still happens in Gmail.
Ask for PureBox connection status first. If Gmail needs attention, the tool result should include a safe PureBox account link. If assistant authorization fails, reconnect the MCP server from the assistant client.