Outbox MCP Server

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

claude mcp add mcp --transport http https://mcp.out-box.dev/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.out-box.dev/mcp"
    }
  }
}

[mcp_servers.mcp]
url = "https://mcp.out-box.dev/mcp"

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.out-box.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.out-box.dev/mcp"
    }
  }
}

This one needs environment variables set before it will start: OUTBOX_API_KEY (Outbox API key (Bearer `outbox_*`). Without it (or the CLI's ~/.outboxrc) the server still starts and every tool asks you to configure it.), OUTBOX_USER (Owner username used as the default `user` argument, skipping a call to /api/me (optional).), OUTBOX_RC (Alternative path to the CLI credential file (default ~/.outboxrc).), OUTBOX_API_BASE (API base URL (everything, including content reads). Default https://api.out-box.dev.), OUTBOX_SITE_BASE (Public site base URL, only used to build the link shown to the human. Default https://out-box.dev.), OUTBOX_TOOLSETS (Toolsets to register: core, comments, library, sharing, keys, teams, automation, apps or all. Default core,comments,sharing.), OUTBOX_FILES_DIR (Folder where the MCP reads/writes files via file_path (nothing outside it). Default ~/Outbox.). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints