Setup guide · MCP

Set up seenpaid in Claude Desktop

Claude Desktop is Anthropic’s desktop app for Claude. Claude cannot post to social media by itself — it has no access to your accounts. Added as a connector, seenpaid gives it the tools to schedule across every channel you connect, check each platform’s limits first, and report what published.

Start your 7-day trial →Jump to the setup

Card required, no charge until day 8. MCP access is on every plan.

Endpoint: api.seenpaid.com/mcp
Transport: Streamable HTTP
Auth: OAuth sign-in
Tools: 50

Four steps

How to connect Claude Desktop to seenpaid

No key to copy — you sign in to seenpaid instead.

1
Have your seenpaid account ready
No API key needed: Claude Desktop signs in to seenpaid with OAuth, and the sign-in decides which workspace it can act on. Start a trial first if you do not have an account.
2
Add seenpaid to Claude Desktop
Open Customize → Connectors, press + and choose Add custom connector, paste the URL and click Add. Leave the advanced OAuth fields empty — seenpaid registers the client itself. Then click Connect and sign in to seenpaid.
Connector URL
https://api.seenpaid.com/mcp
Checked against the official docs: support.claude.com/en/articles/11175166 (custom connectors, OAuth fields only; config file is for local servers) · github.com/geelen/mcp-remote README (--header "Authorization:${AUTH_HEADER}" with env, the documented no-spaces form).
3
Restart and verify
The connector shows as connected under Customize → Connectors. In a new chat, open the tools menu and check that seenpaid is switched on.
4
Ask for your first post
Start with “Which of my social accounts are connected?” — Claude Desktop 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

Prefer an API key? Use the mcp-remote bridge

Claude Desktop’s claude_desktop_config.json only launches local servers — Anthropic’s docs send remote servers through Connectors. To use an sp_ key instead of signing in, run the open-source mcp-remote bridge locally (needs Node.js). Settings → Developer → Edit Config, paste this, then quit and reopen Claude.

claude_desktop_config.json

{
  "mcpServers": {
    "seenpaid": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.seenpaid.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer sp_your_api_key" }
    }
  }
}

Try asking

First things to ask Claude Desktop

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

Which of my social accounts are connected?
Callslist_accounts
Schedule this thread to LinkedIn and Bluesky for Tuesday morning.
Callsget_platform_requirementsschedule_post
What is scheduled for this week, and did anything fail?
Callslist_posts
Which platform is actually worth my time based on revenue, not likes?
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.

I pasted a "type": "http" block into claude_desktop_config.json and nothing happens

That is expected: the config file is for local servers, and Claude Desktop does not connect to remote ones listed there. Use Customize → Connectors, or the mcp-remote block above.

FAQ

Claude Desktop 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.

Open Customize → Connectors, press + and choose Add custom connector, paste the URL and click Add. Leave the advanced OAuth fields empty — seenpaid registers the client itself. Then click Connect and sign in to seenpaid.

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