Seenpaid
com.seenpaidPublished by seenpaid.comOfficial publisherv2.2.0Updated Oct 24, 2026
Agentic social media scheduler: 21 platforms, 50 MCP tools, and which posts made money via Stripe.
Overview
Lets an AI assistant schedule, edit, cancel, and delete social media posts across many connected platforms, and manage the media library behind them.
- What you can do
- Exposes 16 MCP tools for social publishing: list connected accounts and posts, get a single post, schedule or bulk-schedule posts to one, several, or all platforms, update or cancel posts, and permanently delete posts (R29-R36). It also manages media with list_media, add_media_from_url, and a keyless generate_image tool (R37-R39). Account tools cover health checks, connect URLs, disconnecting, platform requirements, and dry-run validation of captions (R40-R44). The README states there is no analytics or revenue tooling in this repository (R46).
- When to use it
- Use it when an assistant should draft, schedule, and publish social posts across multiple platforms from one interface, including bulk scheduling a week of posts (R33). It fits single-operator self-hosted setups where one API key drives both scripts and an agent (R13, R14). It is not for revenue attribution or multi-user teams, which the README says are only in the hosted product (R17, R19).
- Requirements
- Runs as a remote endpoint at over streamable HTTP with OAuth required. The README describes a self-hosted deployment: clone the repository, copy .env.example to .env, set API_KEY and TOKEN_ENCRYPTION_KEY, run docker compose up -d, then run the database migration (R23). The API listens on (R24). MCP clients point at POST /mcp with a Bearer API_KEY (R27). Platform credentials are needed only for the platforms you configure (R76).
Installation
In SourceWeft
- Open Seenpaid in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.seenpaid%2Fseenpaid/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"seenpaid": {
"type": "http",
"url": "https://api.seenpaid.com/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v2.2.0LatestSep 16, 2026
Score
70% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts