POST /api/post
Postbase is a social media publishing tool. Connect your own accounts once, then publish your own posts to any of them: from the console, from your own code over a REST API, or from an AI agent over MCP.
No developer app per network. No OAuth dance per project. No tokens scattered across .env files you are afraid to touch.
{ "platforms": [ "…all eight" ],
"text": "Shipped." }The same publishing, reachable three ways. Whichever you use, it is your account, your words, and access you can withdraw.
console
Compose a post, tick the accounts it goes to, publish now or queue it. Pick who the post is for and it suggests times that are already right for those readers. Every attempt is logged with what each network answered.
rest
One endpoint, one key. Drop it into n8n, a cron job, or whatever already knows when you want to post.
POST /api/post
Authorization: Bearer pb_live_…
{ "brand": "whoamie",
"platforms": ["linkedin", "x"],
"text": "Shipped." }mcp
Postbase is an MCP server. Add it by URL and approve it in the browser, or paste a config with a key — Claude, Cursor and n8n each want a different one. Posting becomes a tool the model can call, revocable whenever you like.
# paste the URL
.../mcp
# or the config
"postbase": {
"url": ".../mcp",
"headers": {
"Authorization":
"Bearer pb_live_…"
}
}It doesn’t read your timeline, your followers, your messages, or anyone else’s posts. It asks for the permissions publishing needs and no others.
It doesn’t collect, sell, or resell your data, and it doesn’t train models on anything you write.
It doesn’t post on its own. Every post comes from you, or from a key you issued and can revoke.
Tokens are encrypted at rest and deleted the moment you disconnect an account, here or from that network’s own settings. Privacy Policy.