Test email verification with GitHub Copilot

VS Code's MCP support (used by GitHub Copilot's agent mode) can call OTPBox directly from a workspace or user config - no extension needed beyond Copilot itself.

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 .vscode/mcp.json:

{
  "servers": {
    "otpbox": {
      "type": "http",
      "url": "https://otpbox.io/mcp",
      "headers": { "Authorization": "Bearer <your-otpbox-key>" }
    }
  }
}

VS Code will prompt to start the server the first time Copilot needs it. Use MCP: Open User Configuration instead of a workspace file to make it available across every project.

Try a prompt

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

"Create a test inbox with otpbox, sign up for this app with it, and get me the verification code."

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 GitHub Copilot docs

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

Next steps

API docs Pricing All guides MCP

← Back to OTPBox