Connect AI agents to your email index

Zipppo speaks MCP (Model Context Protocol).

Everything Zipppo has indexed from your mail — receipts, orders, travel, contracts — becomes a tool your AI agents can use. Claude Code, Cursor, Devin and any other MCP client can search your index, pull one message's derived content, get a deep link that opens the original in Gmail, or ask a question and get a grounded, cited answer. Agents can never send, modify, archive, or delete mail through it. The one write tool, index_message, only adds to your own index — it's how you bring your own sources (WhatsApp, Discord, SMS…) with a reader you run yourself.

Quick start

Sign in and mint a personal token on the MCP page of the app.
Run the one-liner (auto-configures Claude Code and Cursor):

curl -fsSL https://www.zipppo.com/mcp.sh | sh -s -- zpo_YOUR_TOKEN

Manual setup

Claude Code

claude mcp add --transport http zipppo https://mcp.zipppo.com/mcp \
  --header "Authorization: Bearer zpo_YOUR_TOKEN"

Cursor — ~/.cursor/mcp.json:

{
  "mcpServers": {
    "zipppo": {
      "url": "https://mcp.zipppo.com/mcp",
      "headers": { "Authorization": "Bearer zpo_YOUR_TOKEN" }
    }
  }
}

Devin — Settings → MCP Marketplace → Add custom server; paste the URL and the Authorization header above.

The tools

Tool	What it does
`search(query, k, classification?)`	Semantic search over your index. Returns hits with title, summary, sender, date and a Gmail deep link. Optional filter by classification (receipt, contract, …).
`get_item(item_id)`	One indexed message in full: derived text content, summary, and the extracted entities (vendor, amounts, dates, order ids).
`deep_link(item_id)`	A credentials-free Gmail URL that opens the original message.
`ask(question, k)`	A natural-language answer grounded in your mail, with [n] citations and the source items.
`index_message(source, sender, text, timestamp, …)`	Push one message from any source you script yourself into your own index — encrypted, indexed and board-mirrored like email. Writes only to the calling token's account. See bring your own source.

Tokens & security

Personal, revocable tokens. A token grants read-only access to your index and nothing else. Mint up to 10, name them per device or per agent, revoke any time on the MCP page — revocation is immediate.
Shown once, stored hashed. Zipppo keeps only a SHA-256 hash of your token. If you lose it, revoke and mint a new one.
Encrypted index. Your content is encrypted at rest (AES-256-GCM, a key per user). The MCP server decrypts only the items a request touches, in memory, to serve you — the same boundary the indexing worker already has. See the privacy policy.
Rate-limited. Per-user request ceilings, a daily fair-use question allowance (shown on your Billing page), and a daily model budget cap runaway agents. Search calls don't count against the question allowance — only synthesized answers do.

Endpoint

https://mcp.zipppo.com/mcp — streamable-HTTP MCP, stateless, TLS.

Questions? Email schwartzidavid@gmail.com.