Connecting an AI agent

inboxy ships a remote MCP server at mcp.inboxy.net. Any client that speaks Model Context Protocol over HTTPS — Claude, Codex, Copilot, custom clients — can read and search your mail through it.

The server exposes read + manage tools only. There is no send tool, by design (security invariant).

What the agent can do

Tool	Purpose
list_messages	Recent mail, filterable by classification, urgency, address
search	Full-text + semantic search across your messages
get_message	One message — headers, summary, body text (HTML stripped)
get_attachment	Signed URL for one attachment — short-lived, scoped to the asking key
list_addresses	Your @inboxy.net aliases
mint_address	Create a new alias
retire_address	Retire an alias (incoming mail starts bouncing)

Connecting Claude (Desktop / Code)

1. In Account → API keys, mint a new key labelled claude-laptop (or wherever it will live).

2. Copy the plaintext — it's shown once.

3. In your client's MCP settings, add a server:

   • URL: https://mcp.inboxy.net/sse
   • Authorization: Bearer ik_… (the key you just minted)

4. Restart the client. The tools should appear in the agent's tool list.

Connecting other MCP clients

Same shape — point them at https://mcp.inboxy.net/sse with a Bearer token. The server speaks the public MCP spec; no inboxy-specific shim needed.

Browser extensions

For Chrome / Firefox / Edge extensions that want to read inboxy mail without going through an agent, use the browser extension instead — it does device-bound (DPoP) auth, which doesn't need a long-lived bearer key.

Revoking access

If a key leaks, revoke it from Account → API keys. Revocation is immediate — the next request from that key returns 401.