DevInbox

io.devinboxPublished by devinbox.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Real email inboxes for AI agents: create inboxes, catch verification codes, extract OTPs, reply.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

DevInbox gives an AI assistant real email inboxes so it can receive messages, catch verification codes and OTPs, and reply.

What you can do
  • Create and manage real email inboxes for an agent
  • Receive incoming email and read message contents
  • Catch verification codes and extract one-time passwords from delivered mail
  • Reply to messages from an inbox
When to use it
Useful when an agent needs to sign up for or verify a service by email, receive a code or link, or handle simple email replies without a human mailbox.
Requirements
Remote MCP endpoint over streamable HTTP; no local package. Requires a DevInbox API key sent as a bearer token in the Authorization header, obtained from the provider's API key page.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. The server can read incoming mail and send replies, so messages and codes it handles leave your environment and go to the provider. Verification codes and OTPs are sensitive credentials.

Installation

In SourceWeft

  1. Open DevInbox 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/io.devinbox%2Fdevinbox/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": {
    "devinbox": {
      "type": "http",
      "url": "https://mcp.devinbox.io/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

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

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.