Setup guide · MCP

Set up seenpaid in OpenClaw

OpenClaw is an open agent runtime that connects to MCP servers. OpenClaw can call any MCP server you register with it. Adding seenpaid gives its agents a way to publish to your social accounts, check each platform’s rules first, and report back per platform what went out.

Start your 7-day trial →Jump to the setup

$0 due today, cancel anytime. MCP access is on every plan.

$
Endpoint
api.seenpaid.com/mcp
Transport
Streamable HTTP
Auth
Bearer sp_…
Tools
50

Four steps

How to connect OpenClaw to seenpaid

You need a seenpaid API key and one paste.

  1. 1

    Create an API key

    In seenpaid, open Settings → API keys and create a key. It starts with sp_ and is shown once, so copy it straight into the next step. You can revoke it at any time.

    Open Settings → API keys
  2. 2

    Add seenpaid to OpenClaw

    Run this once. openclaw mcp set saves a full server definition; the transport has to say streamable-http, because OpenClaw assumes SSE when it is omitted.

    Terminal
    $ openclaw mcp set seenpaid '{"url":"https://api.seenpaid.com/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer sp_your_api_key"}}'

    Replace sp_your_api_key with your key.

    Checked against the official docs: docs.openclaw.ai/tools/mcp and docs.openclaw.ai/cli/mcp/registry + /transports — mcp set <name> <json>, fields url / transport: "streamable-http" / headers, --auth oauth, mcp login, mcp doctor --probe.

  3. 3

    Restart and verify

    Run openclaw mcp doctor seenpaid --probe. It connects and lists the tools seenpaid exposes. A Gateway running in another process needs its own reload or restart.

  4. 4

    Ask for your first post

    Start with “Which of my social accounts are connected?” — OpenClaw calls list_accounts and names your channels. If none are connected yet, ask for a connect link: that one step needs you in a browser.

Another way

Sign in with OAuth instead

OpenClaw’s docs recommend OAuth over literal bearer tokens in config, and seenpaid supports it. Save the server with --auth oauth, then run the login command and follow the printed URL.

Terminal
$ openclaw mcp add seenpaid \
  --url https://api.seenpaid.com/mcp \
  --transport streamable-http \
  --auth oauth
openclaw mcp login seenpaid

Try asking

First things to ask OpenClaw

Plain requests. Under each one, the seenpaid tools OpenClaw calls to answer it.

  • Which of my social accounts are connected?

    Callslist_accounts

  • Post this to every connected channel and tell me which ones accepted it.

    Callsschedule_postget_post

  • Find posts that got clicks but no sales.

    Callsget_dead_posts needs revenue tracking

  • Rank my channels by revenue per post.

    Callsget_channel_roi needs revenue tracking

Revenue tracking is optional and off by default. Scheduling works without it. Every tool →

Troubleshooting

If it does not connect

401 Unauthorized

The request reached seenpaid but no valid credential came with it. Check the key starts with sp_, was not revoked, and is sent as “Authorization: Bearer sp_…” with the word Bearer and one space. seenpaid also answers 401 when the workspace has no active trial or plan, even with a correct key.

Wrong URL, or the server never connects

The endpoint is exactly https://api.seenpaid.com/mcp — not seenpaid.com, and not an /sse URL. seenpaid speaks Streamable HTTP only; a client set to SSE will not connect. Opening the URL in a browser shows a short explainer page, which is expected.

OAuth or API key — which one?

Config files and command-line clients send the sp_ key as a header. Connector screens in apps (claude.ai, Claude Desktop, ChatGPT, Grok) have no key field: they sign in to seenpaid with OAuth instead. Never paste your key into an OAuth client ID or secret field.

`doctor` warns about a literal sensitive header

It is flagging the key written into config. It still works; to clear the warning, use the OAuth route above or OpenClaw’s secret mechanism for headers.

FAQ

OpenClaw and seenpaid, answered

Not on its own — it has no credentials for your accounts. Connected to seenpaid’s MCP server it can schedule and publish to the 21 platforms seenpaid supports, and report back per platform what went out.

Create an API key in seenpaid under Settings → API keys, then add https://api.seenpaid.com/mcp as a remote MCP server with the key sent as an Authorization: Bearer header. Run this once. `openclaw mcp set` saves a full server definition; the transport has to say streamable-http, because OpenClaw assumes SSE when it is omitted.

Use all 50 seenpaid tools: schedule, edit and cancel posts, check each platform’s limits before publishing, generate images and carousels, and read what published. Revenue tools (which post made money) work only if you switch on revenue tracking, which is optional and off by default.

No. MCP access is included on every seenpaid plan and in the 7-day trial.

It acts through a key or sign-in scoped to one seenpaid workspace; an API key can be revoked in Settings at any time. No tool returns your social passwords or platform tokens, and it cannot connect a new account on its own: it hands you a link and you sign in.

Also works with

Every other setup guide

Same server, same tools. Pick your client for its exact setup.

How the agent works MCP server reference Every way to post from an AI agent Social media MCP servers compared seenpaid for developers