Inboxy MCP server

1. 1
   Open claude.ai/settings/connectors. In the Claude Desktop app it is Settings → Connectors.
2. 2
   Click + Add custom connector.
3. 3
   Name it Inboxy and paste this as the server URL: https://mcp.inboxy.io. Leave the OAuth Client ID and Secret under Advanced settings empty.

   Add custom connector BETA

   Connect Claude to your data and tools.

   Inboxy

   https://mcp.inboxy.io

   1 Name it Inboxy and paste the server URL

   ⌄ Advanced settings

   OAuth Client ID (optional)

   OAuth Client Secret (optional)

   2 Leave OAuth Client ID and Secret empty. Inboxy registers itself.

   Only use connectors from developers you trust. Anthropic does not control which tools developers make available.

   CancelAdd3 Click Add
4. 4
   Inboxy now appears under Connectors. Press Connect.
5. 5
   An Inboxy sign-in page opens in your browser. Sign in, review what Claude will be able to do, and click Allow.

   CONNECT CLAUDE

   Claude wants to use your Inboxy account.

   Read
   See domains, mailboxes, orders, exports and billing Write
   Connect domains, manage tags and sequencers, export mailboxes, cancel mailboxes Billing
   Order mailboxes, add funds, change plans and licenses. Tick this only if you want Claude to spend money for you; it always asks for a confirmation first. Workspaces
   Create workspaces, manage the team and API keys

   AllowCancel
6. 6
   Done. Ask Claude “which of my mailboxes are ready?” or “connect acme-outreach.com and tell me the nameservers”. Access follows your Inboxy login; disconnect any time from Connected apps.

{
  "mcpServers": {
    "inboxy": {
      "url": "https://mcp.inboxy.io",
      "headers": {
        "Authorization": "Bearer <your ibx_k_ key>"
      }
    }
  }
}

Quick setup

Copy the prompt below and paste it into a Claude Code session. Claude Code registers the server and tells you when to sign in.

Set up the Inboxy MCP server in Claude Code for me.

Register it as a streamable-HTTP MCP server named "inboxy" at user scope (so it is available in all my projects), pointing at https://mcp.inboxy.io. No API key is needed: the server uses OAuth. The exact command is:

  claude mcp add --transport http --scope user inboxy https://mcp.inboxy.io

If an "inboxy" server already exists, remove it first with
  claude mcp remove inboxy --scope user
and then add it again so it is not duplicated.

When that is done, tell me to run /mcp, pick "inboxy" and sign in with my Inboxy account, then open a new chat and ask "which of my mailboxes are ready?" to test it.

Manual command

Or run it yourself, then type /mcp inside Claude Code, pick inboxy and sign in:

# Remove an existing entry (if any):
claude mcp remove inboxy --scope user

# Add the Inboxy MCP server:
claude mcp add --transport http --scope user inboxy https://mcp.inboxy.io

claude mcp add --transport http --scope user inboxy https://mcp.inboxy.io --header "Authorization: Bearer <your ibx_k_ key>"

1. 1
   Open chatgpt.com/#settings and click Apps.
2. 2
   Click Advanced settings.
3. 3
   Turn on Developer mode and press Create app.
4. 4
   Name it Inboxy, leave Authentication set to OAuth, and paste this as the Connection URL: https://mcp.inboxy.io. Tick I understand and want to continue and press Create.

   There is no field for an API key or Bearer token. ChatGPT discovers Inboxy's OAuth settings automatically.

   New App

   NameInboxy

   Connection · Server URLhttps://mcp.inboxy.io

   AuthenticationOAuth

   I understand and want to continue
5. 5
   Press Sign in with Inboxy, sign in and click Allow. Then ask ChatGPT about your mailboxes.

Authorization server:  https://api.inboxy.io
Authorize endpoint:    https://api.inboxy.io/oauth/authorize
Token endpoint:        https://api.inboxy.io/oauth/token
Registration:          https://api.inboxy.io/oauth/register  (dynamic, public clients)
PKCE:                  S256 required
Scopes:                read write billing workspaces

Quick setup

Copy the prompt below and paste it into a Codex chat. Codex configures everything for you.

Set up the Inboxy MCP server for me in Codex.

1. Detect my OS.
2. Add a streamable-HTTP MCP server named `inboxy` to my Codex config.toml (~/.codex/config.toml on Mac/Linux, %USERPROFILE%\.codex\config.toml on Windows), URL https://mcp.inboxy.io, bearer_token_env_var = "INBOXY_API_KEY". If an inboxy block already exists, update it instead of duplicating.
3. Then ask me for my Inboxy API key. Tell me I can generate one in the Inboxy app under Settings > API and MCP (the ibx_k_... key is shown once).
4. Set that key as a persistent INBOXY_API_KEY env var for my OS (zsh ~/.zshrc, bash ~/.bashrc, or Windows PowerShell user env var).
5. Tell me to fully quit and reopen Codex, then run /mcp to confirm the Inboxy tools appear.

Or with an API key

1. 1
   Create an API key. Create a key in Inboxy → Settings → API and MCP. The ibx_k_... secret is shown once. A workspace key pins every tool to one workspace; an owner key works across all your workspaces.
2. 2
   Add the MCP server. Open Cursor → Settings → MCP and click + Add new global MCP server. Paste this into .cursor/mcp.json, replacing the placeholder with your key:

   .cursor/mcp.jsonCopy

   {
     "mcpServers": {
       "inboxy": {
         "url": "https://mcp.inboxy.io",
         "headers": {
           "Authorization": "Bearer <your ibx_k_ key>"
         }
       }
     }
   }

3. 3
   Restart Cursor (or run Developer: Reload Window). You should see inboxy under MCP servers with a green indicator.
4. 4
   Use tools. Ask the agent which mailboxes are ready, to connect a domain, or to export mailboxes to Instantly.

1. 1
   Create an API key. Create a key in Inboxy → Settings → API and MCP. The ibx_k_... secret is shown once. A workspace key pins every tool to one workspace; an owner key works across all your workspaces.
2. 2
   Add to VS Code settings. Open settings.json (Cmd/Ctrl + Shift + P → Preferences: Open User Settings (JSON)) and add the MCP server block:

   VS Code settings.jsonCopy

   {
     "mcp": {
       "servers": {
         "inboxy": {
           "type": "http",
           "url": "https://mcp.inboxy.io",
           "headers": {
             "Authorization": "Bearer <your ibx_k_ key>"
           }
         }
       }
     }
   }

   Replace <your ibx_k_ key> with your real key. Copilot discovers the Inboxy tools via MCP automatically.

3. 3
   Restart VS Code. Reload the window (Developer: Reload Window) so Copilot picks up the new server.
4. 4
   Use tools. In Copilot Chat, ask about your domains or mailboxes.

Generic MCP client setup

Inboxy MCP uses the streamable HTTP transport. Any MCP-compatible client can connect with these details:

Server URL:      https://mcp.inboxy.io
Transport:       Streamable HTTP (stateless; no session id)
Authentication:  OAuth 2.1 (sign in, no key)  or
                 Authorization: Bearer <ibx_k_ key>
Discovery:       https://mcp.inboxy.io/.well-known/oauth-protected-resource
                 https://api.inboxy.io/.well-known/oauth-authorization-server

Authentication

OAuth 2.1 (Claude, ChatGPT, Cursor deep link): paste only the server URL. The client discovers Inboxy's authorization server, registers itself and you sign in on Inboxy. No key field.

API key (Codex, VS Code, scripts, most local clients): pass your ibx_k_... key as a Bearer token in the Authorization header.

Create a key

Create a key in Inboxy → Settings → API and MCP. The ibx_k_... secret is shown once. A workspace key pins every tool to one workspace; an owner key works across all your workspaces. Keys carry the scopes you choose: read, write, billing, workspaces.

Run it locally over stdio

{
  "mcpServers": {
    "inboxy": {
      "command": "npm",
      "args": ["run", "mcp"],
      "cwd": "/path/to/infra-api",
      "env": { "INBOXY_API_KEY": "ibx_k_...", "INBOXY_API_URL": "https://api.inboxy.io" }
    }
  }
}