Connect your assistantin about a minute.

1. 1

   Create an API token

   In the dashboard, open Settings → API Integrations and create a token. It is scoped to one workspace — issue a separate token per workspace you want an agent to reach.
2. 2

   Copy the endpoint

   Every client points at the same URL: https://supapush.com/mcp
3. 3

   Paste the config

   Drop the snippet for your client below into its MCP configuration, restart it, and the SupaPush tools appear.

claude mcp add --transport http supapush https://supapush.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

{
  "mcpServers": {
    "supapush": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://supapush.com/mcp", "--header", "Authorization:${SUPAPUSH_AUTH}"],
      "env": { "SUPAPUSH_AUTH": "Bearer YOUR_TOKEN" }
    }
  }
}

Restart Claude, then ask it to list your connected accounts to confirm the connection. Custom connectors on claude.ai sign in with OAuth and have no field for a token, so they cannot connect to SupaPush yet.

{
  "mcpServers": {
    "supapush": {
      "url": "https://supapush.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Keep the token out of a committed file — read it from the environment if the config is in version control.

[mcp_servers.supapush]
url = "https://supapush.com/mcp"
bearer_token_env_var = "SUPAPUSH_API_KEY"

ChatGPT's connectors sign in with OAuth rather than a pasted token, which SupaPush does not offer yet — so ChatGPT on the web cannot connect today. The Codex CLI, and any client that lets you set a header, can.

OpenClaw registers SupaPush as one tool inside a longer running automation — see OpenClaw + SupaPush for the pattern and an example flow.