Test email verification with Gemini CLI

Gemini CLI's settings.json supports remote streamable-HTTP MCP servers - add OTPBox once and every Gemini CLI session in that scope can create and read real test inboxes.

Get a free key Read the MCP docs

Connect OTPBox

Mint a free key first (no account, no card):

curl -X POST https://otpbox.io/api/v1/keys/free -H "content-type: application/json" -d '{}'
→ { "id": "lic_...", "key": "...", "plan": "free", "quotaLimit": 200 }

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "otpbox": {
      "httpUrl": "https://otpbox.io/mcp",
      "headers": { "Authorization": "Bearer <your-otpbox-key>" }
    }
  }
}

Gemini CLI uses httpUrl (not url) for streamable-HTTP servers - a plain url key is treated as the legacy SSE transport and won't connect.

Try a prompt

Once connected, Gemini CLI can call OTPBox's 13 MCP tools directly. For example:

"Use the otpbox MCP server to create a test inbox, sign up for this app with it, then read back the OTP."

What you get

Real inboxes, not mocks

Every code and link comes from a real delivered email, not a stub - so the test proves the actual signup flow works.

Extraction built in

OTP codes and verification links are parsed out automatically. No regex against raw email bodies.

Free tier, no card

200 requests/month with a key minted in one call - no account, no payment info, no waiting.

13 MCP tools

create_test_inbox, wait_for_email, get_otp, get_verification_link, create_test_identity, and more - the full loop is agent-callable.

Official Gemini CLI docs

For Gemini CLI's own MCP setup UI/flags beyond the snippet above, see Gemini CLI's MCP documentation.

Next steps

API docs Pricing All guides MCP

← Back to OTPBox