1
Load demo or connect mail
Start with the one-click synthetic demo. When ready, an administrator can connect approved Google, Microsoft, or IMAP accounts.
One secure connection. Only the inboxes each person should see.
Efficient MCP gives Claude controlled access to permitted client mailboxes for cross-inbox triage, search, live reading, and draft creation—without giving anyone blanket access.
Access administration
How access stays client-specific
Everyone uses the same Efficient MCP connection, but each person signs in separately. The server resolves that identity and applies fresh mailbox permissions before every action.
2
Create each user
Every team member receives an individual Efficient MCP account rather than a shared credential.
3
Delegate exact access
Admins assign metadata-only, read, or read + draft access. A user grant can never exceed the mailbox owner's provider consent.
4
Revoke immediately
Permissions are checked against current server-side grants on every tool call, so revocation applies to the next request.
Delegate conversationally
An admin can tell Claude: “Give alex@example.com read access to Client A.” Claude uses the role-gated admin_set_mailbox_access tool and returns the exact effective scopes.
OAuth stays centralized
The provider refresh token remains encrypted with the mailbox connection. Delegation creates only an Efficient MCP authorization record; no provider credential is copied or revealed.
Revoke on the next call
Ask Claude to revoke the user's access or use Administration. Fresh server-side grant checks make the change effective immediately.
Release capability
What the pilot can do
◫
Mailbox visibility
List only the connected mailboxes granted to the signed-in user, including provider, health, and unread count.
↗
Cross-inbox triage
See what is new across permitted client inboxes and identify unavailable mailboxes without stopping the whole request.
⌕
Metadata search
Search sender, recipient, subject, date, unread state, attachments, and mailbox across permitted accounts.
◎
Live message reading
Fetch a selected message or thread directly from its provider after a fresh authorization check.
✎
Provider-side drafts
Create a draft from an explicitly selected mailbox only when the user has draft permission for that account.
⊘
No send capability
Efficient MCP cannot send email. A person must review and send the draft from the provider mailbox.
Data handling
Useful context, deliberately limited storage
Stored for fast discovery
Mailbox labels and message metadata such as sender, recipients, subject, dates, unread state, and provider identifiers.
Not stored in PostgreSQL
Message bodies, snippets, attachments, and draft content. Bodies are retrieved live and held only for the request.
Protected operational data
Provider refresh credentials and any explicitly enabled legacy IMAP app passwords are encrypted at rest; access decisions and tool activity are audited.
Verification
What has been tested
Release checks completed
27 automated authorization, OAuth, demo, delegation, service, UI-feedback, and HTTP tests
Production TypeScript typecheck and build
OAuth capability presets and provider PKCE challenges
Metadata-only access cannot open message bodies
Admin-only MCP tool discovery and delegation by email/label
Provider consent ceilings block over-delegation
Immediate grant enforcement and revocation behavior
Cloud Run, PostgreSQL, Scheduler, and OAuth discovery health
Release boundary
Ready now—and what comes next
● Ready for pilot use
- Live HTTPS service on Google Cloud
- One-click synthetic demo with no provider credentials
- Provider consent presets: metadata, read, and read + draft
- Individual user delegation through Administration or admin-only MCP tools
- PKCE-protected Google and Microsoft connection flows
- Shared, interactive five-scenario testing guide
◷ Real-provider activation
- The synthetic demo is available immediately after sign-in.
- Google Workspace and Microsoft 365 adapters are implemented.
- Each real provider needs its OAuth application credentials before its consent button can connect accounts.
- Google restricted Gmail scopes require the appropriate consent-screen verification path for external production use.
- Company SSO/MFA and database-level row security remain recommended production hardening.
Ready to test together
Use the interactive guide for the exact setup sequence, suggested Claude prompts, expected results, and revocation test.
Efficient MCP pilot release brief · August 19, 2026. This page describes the currently deployed pilot and is not a substitute for a formal security review, data-processing agreement, or production service-level agreement.