Setup guide · MCP

Set up seenpaid in any MCP client

seenpaid works with any app or agent that implements the Model Context Protocol. seenpaid is a standard remote MCP server, so a client that is not on this list can still use it. You need three facts: the URL, the transport (Streamable HTTP), and one of two ways to authenticate — an API key as a Bearer header, or OAuth 2.1 sign-in.

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
Bearer sp_…
Tools
50

Four steps

How to connect any MCP client 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 any MCP client

    In your client’s MCP settings, add a remote server with these details. If it has a place for headers, use the key. If it only offers sign-in, pick OAuth: seenpaid advertises its authorization server on the first 401 and supports Dynamic Client Registration with PKCE.

    Connection details
    https://api.seenpaid.com/mcp
    Transport
    Streamable HTTP
    Header
    Authorization: Bearer sp_…
    Or
    OAuth 2.1 (DCR + PKCE)

    Checked against the official docs: modelcontextprotocol.io/docs/concepts/transports (Streamable HTTP) · seenpaid’s own server: src/entry-points/mcp/mcp.routes.ts (Bearer sp_ key or OAuth token; 401 carries WWW-Authenticate resource_metadata).

  3. 3

    Restart and verify

    Use your client’s tool list or probe command. A working connection lists seenpaid’s tools; a 401 means the key or sign-in did not reach the server.

  4. 4

    Ask for your first post

    Start with “Which of my social accounts are connected?” — any MCP client 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.

Try asking

First things to ask any MCP client

Plain requests. Under each one, the seenpaid tools any MCP client calls to answer it.

  • Which of my social accounts are connected?

    Callslist_accounts

  • Schedule this post to LinkedIn for Thursday at 9am.

    Callsschedule_post

  • Give me a link to connect my Instagram account.

    Callsget_connect_url

  • What did my posts earn this month?

    Callsget_analytics 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.

My client only supports stdio servers

Then it cannot reach a hosted server directly. The open-source mcp-remote bridge runs locally as a stdio server and forwards to seenpaid with your header — see the Claude Desktop guide for the exact block.

FAQ

any MCP client 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. In your client’s MCP settings, add a remote server with these details. If it has a place for headers, use the key. If it only offers sign-in, pick OAuth: seenpaid advertises its authorization server on the first 401 and supports Dynamic Client Registration with PKCE.

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