MCP server for your support inbox

Connect

Every client connects to one URL:

https://reception.sh/mcp

The first time, your browser opens Reception. Sign in, pick the workspace if you belong to several, and choose what the client may do: Read conversations, people and numbers is always on; Reply and make changes is on by default and can be turned off. Select Allow. The connection stays until you disconnect it; a connection that is unused for 90 days ends by itself.

Clients that only take a header, and your own scripts, use an API key instead.

Claude.ai

Add the connector on claude.ai or in Claude Desktop.

1. Open Customize → Connectors.

2. Select + Add, then Add custom connector.

3. Enter the name Reception and the URL https://reception.sh/mcp, then select Continue.

4. Keep the authentication settings Claude detects and select Continue. Under Authentication, choose Sign in now, keep the suggested OAuth client, and select Add.

5. Sign in and allow access in the Reception window. If no window opens, select Connect next to Reception.

On Team and Enterprise plans, an owner adds the connector once under Organization settings → Connectors (Add, then Custom → Web). Everyone then selects Connect under Customize → Connectors and signs in with their own Reception account. Turn Reception on in a chat from + → Connectors.

Claude Code

claude mcp add --transport http reception https://reception.sh/mcp

Then run /mcp in Claude Code, select reception and sign in in the browser. Add --scope user to the command to use Reception in every project, not only the current one.

Cursor

Add Reception to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "reception": {
      "url": "https://reception.sh/mcp"
    }
  }
}

Cursor signs in to Reception with OAuth: when it does, Reception opens in your browser. Sign in and allow access.

Codex

codex mcp add reception --url https://reception.sh/mcp
codex mcp login reception

Or add the server to ~/.codex/config.toml yourself, then run codex mcp login reception:

[mcp_servers.reception]
url = "https://reception.sh/mcp"

The Codex CLI, the IDE extension and the ChatGPT desktop app share this configuration.

ChatGPT

1. Open Plugins in ChatGPT.

2. Select +, then Add custom MCP server.

3. Enter the name Reception, a short description, and the URL https://reception.sh/mcp.

4. Under authentication, keep the sign-in Reception offers (OAuth), confirm the warning with I understand and want to continue, and select Create as a plugin.

5. Sign in and allow access in the Reception window. In a new chat, type @ and pick Reception.

Whether you can add a custom MCP server, and what it may do, depends on your ChatGPT plan and, in a workspace, on what its admin allows.

API keys

An API key connects scripts and clients that take a header instead of a sign-in.

1. Open Settings → Connections.

2. Under API keys, select Create key.

3. Enter a name, choose Read or Read and write, and create it. The key belongs to you and the current workspace.

4. Copy the key. It starts with rcp_ and is shown once.

Send it as a header:

Authorization: Bearer rcp_…

In Claude Code:

claude mcp add --transport http reception https://reception.sh/mcp \
  --header "Authorization: Bearer rcp_…"

In Cursor, with the key in the RECEPTION_API_KEY environment variable:

{
  "mcpServers": {
    "reception": {
      "url": "https://reception.sh/mcp",
      "headers": { "Authorization": "Bearer ${env:RECEPTION_API_KEY}" }
    }
  }
}

In Codex, with the same environment variable:

[mcp_servers.reception]
url = "https://reception.sh/mcp"
bearer_token_env_var = "RECEPTION_API_KEY"

Keys don't expire, and you can hold up to 10 per workspace. Treat one like a password: anyone with it acts as you. Don't put a personal key in a shared Claude Team or Enterprise connector, where everyone would use it.

Tools

The agent picks tools by itself; ask in your own words, such as "Which chats are waiting for an answer?" or "Reply to Maya that the fix ships Friday." Write tools act as you: a reply appears in the person's chat as yours, with a push when the app has push set up, as from the inbox.

Inbox

People

Apps and numbers

AI knowledge

Automations

Automations are always switched on in the dashboard. The result of create_automation links to the automation and, for events your app reports, includes the track line to add.

Prompts

Prompts are ready-made requests. Clients that support them list them as commands; in Claude Code, type / and pick one, such as /reception:daily_overview.

Permissions

Every tool runs with your permissions in the dashboard, in the workspace you connected. Members can read, reply and manage conversations; app numbers, AI knowledge and changes to automations need an Admin. A connection with read access only can't send or change anything. Sending messages follows the same subscription rule as the inbox.

What stays in the dashboard

Through MCP you can't create or delete apps, delete, block or reset people, delete conversations, add or edit links, paywalls or review texts, switch automations on, change integrations, push or Telegram settings, the chat's appearance, billing, members or the identity secret. These stay in the dashboard.

Conversations an agent reads go to that client's AI provider, under its terms. See Data & privacy.

Disconnect

Open Settings → Connections. Select Disconnect next to a connected app, or Revoke next to an API key. It stops working with its next request. Leaving or being removed from a workspace disconnects all your connections there.

Removing Reception in the client alone doesn't always end the connection on our side. Disconnect it in Reception as well.