Setup guide · MCP

Set up seenpaid in Muse

Muse is Meta’s personal AI agent, in its own app, on muse.ai and in WhatsApp. Muse runs errands across your digital life, but it has no connection to your social channels until you give it one. seenpaid is not in Meta’s connector directory: we submitted a listing on 20 September 2026 and it has not been approved. You do not have to wait for that — Muse builds a custom connector for you from any MCP server URL, and seenpaid is a hosted MCP server, so the route below works today. Muse itself is United States only and 18+ at launch.

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 Muse 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 Muse

    Ask Muse, in plain words, to add a custom connector for this URL — for example “Add a custom connector for https://api.seenpaid.com/mcp”. Muse asks whether the server needs a key: paste a seenpaid key from Settings → API keys and it is sent as an Authorization: Bearer header. seenpaid also accepts OAuth 2.1 sign-in, but Meta publishes no connector config format — Muse writes and tests the connector itself — so we document the key, which we know the server accepts, rather than a screen we cannot describe. Nothing to edit on your side.

    Connector URL
    https://api.seenpaid.com/mcp

    Checked against the official docs: muse.ai/platform — Meta’s connector platform, opened 18 September 2026 (submit, review, directory). It publishes no config-file format, because Muse builds each connector itself from an MCP server URL, so none is invented here. Muse’s launch terms (8 September 2026, United States, 18+) are Meta’s own. seenpaid’s directory submission: 20 September 2026, status submitted, not approved.

  3. 3

    Restart and verify

    Ask Muse “which of my social accounts are connected?”. It should reach seenpaid and name your channels instead of answering from memory. A connector Muse built successfully is saved as one of its skills, so it appears in what it can do.

  4. 4

    Ask for your first post

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

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

  • Which of my social accounts are connected?

    Callslist_accounts

  • Schedule this to LinkedIn and Bluesky for tomorrow at 9am.

    Callsschedule_post

  • Will this caption fit everywhere I post?

    Callsget_platform_requirementsvalidate_post

  • What is scheduled for this week?

    Callslist_posts

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.

seenpaid is not in Muse’s connector directory

That is correct, and we will not pretend otherwise: the listing was submitted to Meta on 20 September 2026 and has not been approved. A custom connector needs no approval — Muse builds it for your account only — which is why the steps above are the ones that work today.

Muse is not available where I am

Muse launched on 8 September 2026 for adults in the United States only, across its app, muse.ai and WhatsApp. Meta has said more countries will follow. Until it reaches yours, the same seenpaid server works in every other client on this page.

Muse answers about my posts without calling seenpaid

Name the connector in the request — “use seenpaid to schedule…”. A custom connector is one skill among many, and being explicit is what makes it reach for the right one.

FAQ

Muse 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. Ask Muse, in plain words, to add a custom connector for this URL — for example “Add a custom connector for https://api.seenpaid.com/mcp”. Muse asks whether the server needs a key: paste a seenpaid key from Settings → API keys and it is sent as an Authorization: Bearer header. seenpaid also accepts OAuth 2.1 sign-in, but Meta publishes no connector config format — Muse writes and tests the connector itself — so we document the key, which we know the server accepts, rather than a screen we cannot describe. Nothing to edit on your side.

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