Docs / Quickstart

Your agent, talking to us in two minutes

This website runs a live Model Context Protocol (MCP) server at https://envoltmail.com/mcp. It is read-only, needs no key and is rate-limited per address. Use it to see what an agent-ready mail service feels like before the mailbox interfaces open.

1. Connect a client

Any client that speaks Streamable HTTP works. In a client that reads a JSON server list:

{
  "mcpServers": {
    "envolt-mail": { "type": "http", "url": "https://envoltmail.com/mcp" }
  }
}

Or from a terminal with Claude Code: claude mcp add --transport http envolt-mail https://envoltmail.com/mcp.

2. Or call it directly

It's JSON-RPC 2.0 over POST, so plain curl is enough:

curl -s https://envoltmail.com/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"search_docs","arguments":{"query":"kill switch","limit":2}}}'

3. The three tools

get_status
Every capability marked live, staging or designed, plus the roadmap. Optional state filter. Ask your agent: "What does Envolt Mail actually run today?"
search_docs
Full-text search over this site, returning URLs, titles and Markdown excerpts. query (2–200 characters), optional limit 1–5.
verify_agent_seal
Check an Envolt-Agent-Seal header with our verifier against a key document you supply. Nothing is fetched. Pass dkim_covers_seal: true only if your own DKIM check confirmed it; otherwise the best possible answer is "unverified". The header format.

Things to ask your agent

What comes next

The mailbox interfaces, a REST API and an MCP server with a scoped key per mailbox, run in staging on synthetic mail. They can read conversations and propose replies, never send. See their tools, or request early access to build against them first.

Prefer reading to calling? Every page has a Markdown twin (add .md), and llms.txt indexes them all.