MCP setup
Connect your assistantin about a minute.
One endpoint, one token, and the same set of tools in every client. Below is the exact configuration for the four we see most often.
Before you start
- 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
Copy the endpoint
Every client points at the same URL:https://supapush.com/mcp - 3
Paste the config
Drop the snippet for your client below into its MCP configuration, restart it, and the SupaPush tools appear.
Claude
Claude Desktop reads a JSON config file; Claude Code takes the same server definition.
{
"mcpServers": {
"supapush": {
"url": "https://supapush.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Restart Claude, then ask it to list your connected accounts to confirm the connection.
Cursor
Add the server in Cursor's MCP settings, or commit it to the project.
{
"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.
ChatGPT & Codex
ChatGPT connects through a custom connector; the Codex CLI takes a TOML entry.
[mcp_servers.supapush]
url = "https://supapush.com/mcp"
headers = { Authorization = "Bearer YOUR_TOKEN" }In ChatGPT, add SupaPush as a connector pointing at the same URL and supply the token as the authorization header.
OpenClaw
OpenClaw registers SupaPush as one tool inside a longer running automation — see OpenClaw + SupaPush for the pattern and an example flow.
If something does not connect
No tools appear
401 on every call
Bearer doubled. Reissue it from Settings.Empty account list
Start posting from one calendar
Every plan includes a 7-day free trial. Connect real accounts, publish real posts, and stop whenever you like.
Get Started For Free