Seenpaid MCP server

seenpaid

Ask your AI agent which of your posts made money.

That question is answered by seenpaid.com — the hosted cloud product, which matches your Stripe sales back to the exact post that drove them. This repository is not that. This repository is the open posting layer underneath it: a self-hosted service that ships 25 platform adapters, queues and retries deliveries, and exposes itself to an AI agent over MCP (Model Context Protocol) so an agent can schedule posts on your behalf. Point an agent at your own instance, or point it at seenpaid.com if you also want the revenue answer — same MCP shape, different depth.

What this is

every connected platform as an independent, retried job.

• A BullMQ-backed publish pipeline: schedule a post once, it fans out to

paste-your-own-credentials flows, whichever each platform actually uses. (The hosted product, seenpaid.com, advertises 21: the ones a customer can connect there without registering their own developer app. Self-hosting you bring your own credentials, so you get all 25. Two different numbers, both honest — don't quote one as the other.)

• 25 platform adapters behind one interface — OAuth, webhook, API-key, and

account health — so both a script and an AI agent can drive it the same way.

• A REST API and a 16-tool MCP server — scheduling, editing, media, and

concept. Deploy it, set a key, use it.

• Single-operator by design: one API key, no login screen, no multi-tenant

What this is NOT

or tell you which post earned anything. That's the hard, hosted part — seenpaid.com — and it's deliberately not in here.

• No revenue attribution. This repo does not track clicks, match sales,

If you need that, you're looking for the cloud product.

• No multi-user accounts, teams, or roles. One instance, one operator.

is software you run, not a subscription.

• No billing, plans, or usage limits. There's nothing to meter — this

If what you actually want is "which post made money," this repo alone can't answer that — connect your instance's data to seenpaid.com, or read SELF_HOST.md for the honest tradeoffs before you invest time self-hosting for that reason.

Quickstart

git clone <this-repo>
cd seenpaid
cp .env.example .env
# fill in API_KEY and TOKEN_ENCRYPTION_KEY (openssl rand -hex 32 for each)
docker compose up -d
docker compose exec api npm run db:migrate

The API is now listening on http://localhost:3001. Full walkthrough, including connecting a platform and your agent, in SELF_HOST.md.

The 16 MCP tools

Point an MCP-capable agent at POST /mcp (Bearer API_KEY) and it gets:

Shortened. The full README is on GitHub.