inboxy

net.inboxyPublished by inboxy.netOfficial publisherv1.0.1Updated Oct 24, 2026

Read and manage your @inboxy.net aliases, mail and RSS feeds; compose mail on paid plans.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server for inboxy that lets an assistant read, search, summarize, reply to and send mail through @inboxy.net aliases, plus manage RSS feeds and…

What you can do
  • List, read, search, render, keep, delete and send mail, and inspect what the agent has sent
  • Manage RSS subscriptions and the articles inside those feeds
  • Mint and retire @inboxy.net aliases
  • Check plan, quota, rate limits and retention, and configure scheduled digests
  • Bulk-change read state across mail and feeds
When to use it
Useful when you want an assistant to triage, summarize or answer email without giving it access to your real mailbox, or to manage disposable aliases and RSS feeds. Suited to both interactive clients with OAuth sign-in and unattended agents using a scoped API key.
Requirements
A hosted remote endpoint over Streamable HTTP; nothing to install. Interactive clients sign in with OAuth 2.1 (Dynamic Client Registration and PKCE). Unattended agents need a static bearer API key created under Account → API keys, optionally scoped to one alias. An inboxy account is required.
Before you install
The assistant can send, delete and bulk-modify mail and aliases; destructive tools are annotated so clients can require confirmation. Sending mail debits a per-user quota and is only available on paid plans. Outbound mail carries an inboxy attribution footer, and message bodies are retained 90 days by default unless pinned. A leaked API key exposes the aliases it is scoped to; revoke grants and keys in the account settings.

Installation

In SourceWeft

  1. Open inboxy 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/net.inboxy%2Finboxy/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": {
    "inboxy": {
      "type": "http",
      "url": "https://mcp.inboxy.net/"
    }
  }
}

README

inboxy — remote MCP server

Endpoint: https://mcp.inboxy.net · Transport: Streamable HTTP · Registry: net.inboxy/inboxy

inboxy is a privacy-first email aliasing service with an AI-readable inbox. This server exposes your @inboxy.net mail, RSS feeds, and aliases to any client that speaks the Model Context Protocol, so an assistant can read, search, summarise, and reply to your mail without ever touching your real mailbox.

This repository is documentation. The server is hosted — there is nothing here to install, build, or run, and no npm package to pull. It exists so the registry listing has a home and so the connection details are versioned somewhere public. The implementation is closed-source.

Connecting

Most clients need only the URL. The server speaks OAuth 2.1 with Dynamic Client Registration and PKCE, so interactive clients need no API key:

json
{  "mcpServers": {    "inboxy": {      "url": "https://mcp.inboxy.net"    }  }}

Claude Desktop: Settings → Developer → Edit Config, paste the above, restart, and sign in when redirected. Claude Code and other MCP clients take the same URL and run the OAuth flow themselves.

Unattended agents (OpenClaw, Hermes, Codex, CI) use a static bearer key instead, minted under Account → API keys:

Authorization: Bearer ik_…

Keys can be address-scoped to a single alias. A scoped key sees only that alias's mail, has its outbound From: pinned to it server-side, and is refused for account-wide operations — so a leaked key exposes one alias, not the account.

Full setup, including the per-client config quirks that bite (OpenClaw's --header uses Name=Value, Hermes' YAML uses Name: Value), is at https://inboxy.net/help/connect-mcp.

What an agent can do

48 tools as of v1.0.0, across eight groups, named <group>_<action> so clients render them under a common heading:

GroupCovers
mail_*List, read, search, render, keep, delete, and send mail
outbox_*Inspect what the agent has sent
feed_*RSS subscriptions
article_*Articles within those feeds
address_*Mint and retire @inboxy.net aliases
account_*Plan, quota, rate limits, retention
digest_*Scheduled digest settings
mark_*Cross-domain bulk read-state

Every tool declares an MCP behavioural annotation — read-only, idempotent, or destructive — so clients can gate the destructive ones behind confirmation.

The canonical, always-current tool reference is https://inboxy.net/help/connect-mcp — deliberately not duplicated here, so it cannot drift.

What an agent can send

inboxy gives your AI an inbox, not your Gmail. Every outbound path is scoped server-side, so a leaked credential cannot become a spam cannon:

ToolRecipient ruleCap
mail_replyLocked to the original sender of the message being replied to5/hour
mail_forwardLocked to your own verified personal emailIdempotent
mail_sendAny recipient, minus self-loops and reserved local-partsDebits per-user send quota
mail_inviteAny external address that isn't already an inboxy user10 per rolling 30 days

No surface anywhere accepts a caller-supplied From:. Mail is always sent from one of your own aliases, never from your real address.

@inboxy.net → @inboxy.net mail is delivered in-network with no SMTP egress. Anything leaving the network carries a one-line — inboxy.net — agentic email attribution footer, injected at a single point so every send path behaves identically.

Privacy

  • EU data residency. Storage and compute are pinned to Cloudflare's eu jurisdiction.
  • Scoped embeddings. Semantic search runs on per-user vectors.
  • 90-day default retention on message bodies; pinned messages are exempt.
  • Short-lived tokens. Refresh tokens rotate per OAuth 2.1 §4.3.1.
  • Revoke an OAuth grant under Account → MCP / OAuth clients, or a key under Account → API keys. Revocation takes effect on the next request.

Privacy policy · Terms

Registry manifest

server.json is the manifest published to the official MCP registry under net.inboxy/inboxy. Its version tracks the version this server announces to clients on initialize.

Support

[email protected] · Security disclosures: [email protected] (security.txt)

License

The contents of this repository are licensed Apache-2.0. See LICENSE.

Source: README.md at commit ba219fd

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.1LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.