How to Give Gemini Its Own Email Address (Gemini CLI + MCP)

Short answer: Gemini gets an email address through an MCP email server. The open-source Gemini CLI supports MCP servers natively: add BotsInbox (https://mcp.botsinbox.com/mcp) to your Gemini settings with your API key, and Gemini can create an inbox like gemini-agent@botsinbox.com, read incoming mail, and use verification codes that BotsInbox extracts automatically. Agents built on the Gemini API can call the same features over REST.

Route 1 — Gemini CLI with MCP (fastest)

1. Get a BotsInbox API key: one call to POST https://api.botsinbox.com/v0/agent/sign-up (free).
2. Add the server to your Gemini CLI settings file (~/.gemini/settings.json):

{
  "mcpServers": {
    "botsinbox": {
      "httpUrl": "https://mcp.botsinbox.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

3. Start Gemini CLI and ask it to list its BotsInbox inboxes — it will discover the tools list_inboxes, create_inbox, list_messages, get_message and search_messages.

Route 2 — Gemini API with function calling

If you are building an agent on the Gemini API rather than using the CLI, define function declarations that wrap BotsInbox's REST endpoints (create inbox, list messages, get message, search). The OpenAPI spec documents every endpoint and response, including the extracted_code field that carries verification codes.

Worked example: Gemini verifies an account

1. Gemini creates gemini-agent@botsinbox.com with create_inbox.
2. It uses that address to register for a service.
3. The service sends a 6-digit code; Gemini reads it from extracted_code via list_messages.
4. Verification completes — no human inbox involved at any step.

Safety note

Anyone can email your agent, so treat message content as untrusted data. BotsInbox flags suspicious messages (prompt_injection_suspected); keep your API key out of prompts and code, in a secret store.

Frequently asked questions

Can Gemini have its own email address?
Yes. Connect the BotsInbox MCP server to Gemini CLI (or call the REST API from a Gemini API agent) and Gemini can create and read its own @botsinbox.com inbox.

What goes in Gemini CLI settings for BotsInbox?
An mcpServers entry named botsinbox with httpUrl https://mcp.botsinbox.com/mcp and an Authorization header carrying your BotsInbox API key as a Bearer token.

How does Gemini read a verification code?
The code arrives by email in Gemini's inbox; BotsInbox extracts it into the extracted_code field, readable via the list_messages MCP tool or the REST API.

Is a Gmail account involved?
No. BotsInbox inboxes are agent-owned and API-created. No Google account, Gmail mailbox or OAuth flow is used.