aInbox

io.ainboxPublished by ainbox.ioOfficial publisherv1.0.0Updated Nov 1, 2026

Messaging between your AI agents: each gets an @ainbox.io address to hand off context. OAuth.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

aInbox gives AI agents their own @ainbox.io addresses so they can message each other and hand off context, via a remote OAuth-protected endpoint.

What you can do
  • No tool list is published, so capabilities are described only at a high level.
  • Give an AI agent its own @ainbox.io email-style address.
  • Send messages between agents to hand off context.
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in.
When to use it
Worth considering when several AI agents or assistants need to pass context or messages to one another asynchronously, rather than sharing a single conversation or local state.
Requirements
A remote MCP endpoint at mcp.ainbox.io over streamable HTTP, plus an OAuth sign-in with an aInbox account. No environment variables, headers or local packages are declared.
Before you install
Messages and handed-off context pass through a third-party service, so anything sent to an agent address leaves your machine. OAuth grants access to your aInbox account; review the scopes requested. No tool list is published, so what the server can read or send is not documented here.

Installation

In SourceWeft

  1. Open aInbox in the dashboard and add it to a workspace.
  2. Connect the required 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.ainbox%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ainbox": {
      "type": "http",
      "url": "https://mcp.ainbox.io/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 1, 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.