zoomfort MCP server

zoomfort MCP server

Receive-only inbox for AI agent sign-ups: one call returns the verification code. Never sends.

zoomfort gives an AI agent its own email address. The agent signs up for a service with that address, then asks zoomfort for the verification code or link. zoomfort only receives mail: it cannot send, reply or forward, and it never opens or follows links in mail.

This repository holds the public description of the hosted MCP server: this README, the registry file server.json and an agent usage file, skills/zoomfort/SKILL.md. The server itself runs at https://mail.zoomfort.com/mcp; there is nothing to install or self-host.

• Website: https://zoomfort.com
• Documentation: https://zoomfort.com/docs
• Privacy policy: https://zoomfort.com/privacy
• Terms: https://zoomfort.com/terms

Access

Create a free account at https://zoomfort.com/app/signup. New accounts open every day; when the day's places are taken, register interest at https://zoomfort.com/#invite or email hello@zoomfort.com and we will send you an invite. Once your account exists, sign in at https://mail.zoomfort.com/app and create an address, such as signup@yourname.zoomfort.com. Mail to an address you have not created is refused.

Tools

Four read-only tools, each marked readOnlyHint: true:

The tools cannot send, delete, move or mark mail, and do not return raw mail, headers or attachment content.

Connect over MCP

Endpoint: https://mail.zoomfort.com/mcp, Streamable HTTP, POST only. Use this exact path: /mcp/ with a trailing slash does not work.

Claude (OAuth). Open Settings › Connectors › Add custom connector, enter https://mail.zoomfort.com/mcp and approve the connection on zoomfort. You choose which addresses it can read and whether it can read codes, mail or both. A connection counts as one of your keys, expires after 90 days without use, and can be disconnected any time in Settings › API keys.

Other clients (API key). In zoomfort, open Settings › API keys › Create key, give it read:codes (add read:mailbox if the agent should list mail) and only the addresses it needs. The full key is shown once. Keep it in the environment as ZOOMFORTAPIKEY and send it as Authorization: Bearer . Never put the key in a URL or in tool arguments.

Cursor, .cursor/mcp.json:

{
  "mcpServers": {
    "zoomfort": {
      "url": "https://mail.zoomfort.com/mcp",
      "headers": { "Authorization": "Bearer ${env:ZOOMFORT_API_KEY}" }
    }
  }
}

Claude Code, .mcp.json:

{
  "mcpServers": {
    "zoomfort": {
      "type": "http",
      "url": "https://mail.zoomfort.com/mcp",
      "headers": { "Authorization": "Bearer ${ZOOMFORT_API_KEY}" }
    }
  }
}

Codex, ~/.codex/config.toml:

[mcp_servers.zoomfort]
url = "https://mail.zoomfort.com/mcp"
bearer_token_env_var = "ZOOMFORT_API_KEY"

These client examples follow each vendor's documentation and have not all been tested end to end.

Or use the REST API

The same lookups are plain HTTPS calls with the same key:

curl --get 'https://mail.zoomfort.com/api/v1/code' \
  -H "Authorization: Bearer $ZOOMFORT_API_KEY" \
  --data-urlencode 'to=signup@yourname.zoomfort.com' \
  --data-urlencode 'from_domain=service.example' \
  --data-urlencode 'since=2026-10-17T08:00:00Z' \
  --data-urlencode 'wait=25'

Shortened. The full README is on GitHub.