BotsInbox — Email Inboxes for AI Agents

com.botsinboxPublished by botsinbox.comOfficial publisherv1.5.1Updated Nov 7, 2026

Free email inboxes for AI agents: self sign-up, receive email and verification codes.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP service that gives an AI agent its own free email inbox for receiving messages and verification codes.

What you can do
  • Provides an email inbox that an AI agent can sign up for on its own.
  • Lets the agent receive incoming email messages.
  • Lets the agent retrieve verification codes sent by email.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Useful when an agent needs an email address to complete sign-ups or receive confirmation and verification codes during automated workflows.
Requirements
A remote endpoint at mcp.botsinbox.com over streamable HTTP. A bearer token supplied in the Authorization header is required.
Before you install
The service requires a bearer credential in the Authorization header, so keep that token private. Inbox contents and any codes received pass through a third-party service; avoid using it for sensitive accounts or confidential mail.

Installation

In SourceWeft

  1. Open BotsInbox — Email Inboxes for AI Agents in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.botsinbox%2Fbotsinbox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "botsinbox-email-inboxes-for-ai-agents": {
      "type": "http",
      "url": "https://mcp.botsinbox.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

3
  1. v1.5.1LatestNov 7, 2026
  2. v1.4.0Nov 5, 2026
  3. v1.3.0Nov 3, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.