Your Privacy Suite.
In Your AI Agent.
AI access without loose secrets
The MCP server gives agents the account controls they need while keeping private content outside the tool boundary.
OAuth Connector Flow
Agents connect through sign-in and consent. You never paste a long-lived API key into a third-party client.
Alias Automation
Create, list, toggle, and delete aliases from natural-language workflows and agent tasks.
Recipient Management
List verified inboxes and add new recipients while verification stays under your control.
Drop Metadata
List, disable, re-enable, and delete drops without exposing filenames, files, or decryption keys.
Standard MCP Transport
Use the modern Streamable HTTP transport with clients that support custom MCP connectors.
Encrypted Data Stays Private
Vault-encrypted notes, labels, drop names, and file contents remain unreadable to AI clients.
Typed tools,
clear boundaries
MCP turns everyday privacy operations into explicit tool calls. Agents can work on the control plane, but encrypted content stays protected by anon.li's browser and vault encryption model.
list_aliases | Review active aliases, counters, and timestamps |
create_alias | Generate random or custom aliases for new services |
toggle_alias | Pause or restore an address by ID or email |
list_recipients | Check verified forwarding destinations |
list_drops | Inspect encrypted drop metadata without file contents |
delete_drop | Clean up old drops and reclaim storage quota |
Connect in three steps
From connector URL to first agent task in minutes.
Add
Use https://anon.li/api/mcp as the custom connector URL in your MCP-compatible client.
Authorize
Sign in to anon.li, complete 2FA if enabled, and approve the OAuth consent screen.
Delegate
Ask your agent to create aliases, review recipients, or clean up drop metadata.
Ready to connect your agent?
Add the MCP endpoint, authorize through anon.li, and keep encrypted content outside the agent boundary.