Publora
The social media API for AI agents. MCP-native.
882 followers
The social media API for AI agents. MCP-native.
882 followers
Publora gives your AI a full engagement loop on social media: post, comment, react, @mention — all via MCP/API, across 10 networks (LinkedIn, X, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, Telegram). Works with Claude, Cursor, OpenClaw, or your own agent.
Free tier, $2.99/account, npx-installable Skills. Stop wiring 10 OAuth flows - ship the agent.
This is the 2nd launch from Publora. View more
Publora
Launching today
Publora is a publishing API for 10 social platforms. One REST API call handles multi-network distribution — no SDKs, no OAuth wiring. The native MCP server with 18 tools gives AI agents like Claude and Cursor a full engagement loop: post, comment, react, pull analytics — across LinkedIn, X, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, and Telegram
Free Options
Launch Team
Publora
Hey Product Hunt! 👋 Jane here, CEO of Publora.
Publora has been around for a while - you might have even seen us here before.
We started as a social media scheduler for people. But this launch is different.
So we evolved Publora into something that works both for humans and for agents.
AI agents are everywhere now and the marketers, content managers, and creators we work with aren't just writing posts in tools anymore - they're building workflows where agents do the heavy lifting.
Publora now works for humans and AI agents equally well:
One API call publishes to 10 platforms - your code, your agent, your choice
MCP server lets agents post, schedule, and manage content in plain language
Comments and replies are in the API too - not just publishing, full engagement
Works inside the tools where you already operate - no tab-switching
Unlike most social tools built for clicking buttons, Publora is built for automation first. No browser bots. No workarounds. Official APIs only.
Whether you're a content manager building your first agent workflow, or a developer shipping a social automation - Publora fits in without friction.
Pricing starts at $2.99/account/month. And as a thank you to the Product Hunt community — use code PH20THANKU for 20% off your first payment.
We're happy to answer your questions - drop them below!
Scade.pro
@eugenia_ivanova3 Great project! Good luck with the launch, and thanks for the promo code.
Publora
@maria_anosova Thank you so much! Hope the promo code comes in handy — would love to hear what you think once you try it! 😊
@eugenia_ivanova3 great Project Eugenia, this is a bit random but do you know if this impacts the algo by any way when posting?
Publora
@bashir_bandi We haven't noticed any impact! 😊
@eugenia_ivanova3 Congrats on the launch today!! This has me genuinely excited. My only question is about LinkedIn - I live there and I know how freaky it can be about anything that connects to it. And that makes me concerned about anything that can negatively impact me there. How does Publora handle that?
@anna_ludwinowski totally hear you — LinkedIn is the one platform people are right to be careful with!
Good news: we go through LinkedIn's official API with an approved developer account, not browser automation or any scraping/unofficial tricks. That distinction is everything.
The stuff LinkedIn actually cracks down on is tools that fake activity or auto-generate engagement. Publora doesn't do that — it just publishes the content you (or your agent) create, through the sanctioned API, exactly the way LinkedIn intends posts to come in. So there's nothing "connected" to your account doing anything sketchy in the background.
@ilya_makarov3 Ok good to know! How does it work with the analytics, though?
@anna_ludwinowski
Analytics are live for LinkedIn right now (other platforms are on the roadmap), and they cover the posts you publish through Publora — the numbers come straight from LinkedIn's official API, so they match exactly what you'd see natively. For any post you've sent through us you can pull: impressions, unique reach (members reached), reactions, comments and reshares — per-post or aggregated across your account. And since it's all exposed through the MCP, you can just ask your agent "how did my last LinkedIn post do?" and it'll fetch the live stats and break down engagement for you — no dashboard digging. Full details here: https://docs.publora.com/guides/linkedin-analytics So you get the safety of official-API posting and the numbers to see what's actually working.
PopTask
@eugenia_ivanova3 very interesting 🙌🏽 btw, does the mcp server handle rate limits / token refresh per platform, or is that on me to manage in the workflow?
Publora
@lilhadi We handle all of that on our side. 😊
Exposing 18 distinct tools across 10 networks inside a single MCP server is incredibly powerful. How do you optimize the tool schemas to prevent LLMs (like Claude in Cursor or Claude Code) from getting 'tool fatigue' or hallucinating arguments when trying to orchestrate complex, multi-platform actions like cross-posting to both X and Bluesky simultaneously?
@nurlyzhann
The short version: we push all the constraints down to the schema layer, not the prompt — so the model can't really get this wrong.
A few specifics:
• Every closed value set is a z.enum, so a hallucinated argument dies in Zod validation before it ever reaches the API — the LLM gets an immediate, typed error to correct from instead of a silent bad call.
• Opaque platform IDs are only accepted verbatim from a paired list_connections discovery call — the field description literally says "do NOT invent or guess IDs", so there's nothing for the model to make up.
• Cross-posting to X + Bluesky (or all of them) is a single create_post with a platforms[] array. The per-network fan-out happens server-side, so the model never has to reason about platform differences at all — it just says "post this, to these".
That combo is what keeps it from turning into 18-tools-worth of cognitive load: the agent reasons about intent, the schema + server handle correctness. Happy to nerd out more if you're building in this space!
Most "publish anywhere via API" tools work fine until you hit rate limits, token refresh edge cases, or a platform that quietly changed its media upload flow. Curious whether Publora owns the per-platform adapter layer or expects developers to handle that messiness themselves.
I know how complicated it could be to implement external APIs
Congrats for the launch
@fberrez1 Exactly. Our goal is to remove that headache completely.
Developers and agents just create the content and send it to Publora. Everything else — platform-specific APIs, token refreshes, rate limits, media upload quirks, and API changes — is handled on our side.
Publora
@fberrez1 Thank you for the kind words and great question! Ilya covered it perfectly. 😊
Interesting concept, since this uses API, is the primary use case via scripts / agents ? like I need to create a scheduled job ? how often I need to refresh my oauth credentials ? do you also support analytics w.r.t engagement on each platform ?
Publora
@vinitvr Good questions!
- Use case: both. Agents call it via MCP; scripts hit the REST API directly. There's also a dashboard if you'd rather not write code.
- Scheduled job: no cron on your side — scheduling is built in (queue posts ahead of time), or fire on-demand from your agent/script.
- OAuth: you don't refresh anything. Connect an account once and we rotate/refresh the tokens in the background — you only re-auth if you revoke access.
- Analytics: yes — per-post engagement (likes/comments/views) LinkedIn only.
@sergebulaev , great thanks, will check it out.
Publora
@vinitvr Serge covered it perfectly! And if you ever get stuck setting things up — we're here. 😊
@eugenia_ivanova3 sure, thanks !
@michael_vavilov At the moment, we don’t expose proxy/IP geo selection to users. Our infrastructure currently runs from the US (Virginia).
That said, it’s a great point. We know that for TikTok, not only the country but often even the publication location can affect distribution. We’ve also seen creators deliberately optimize for local presence.
We’re definitely thinking about adding support for publishing through residential proxies and allowing users to choose the target country (or even city) in the future.
The MCP angle is what makes this genuinely interesting, most social APIs stop at "publish a post" but the full engagement loop (comment, react, mention) is what agents actually need to run a real presence. The $2.99/account pricing removes the usual "is this worth wiring up" hesitation. One question: for Instagram specifically, does it support carousel posts and reels scheduling, or only single images/text for now?
Publora
@keirodev Both Instagram features are fully supported! 😊
@eugenia_ivanova3 Perfect, that's exactly what I needed to hear :) Adding it to my stack to test for my own app's social presence. Thanks for the quick answer!
Publora
@keirodev Awesome, can't wait to hear how it goes! 🚀
Congrats on shipping!
Is it possible to use Publora under the hood of my own product, white-label style? So my clients hook up their own channels, but it all sits under my account.
@timur_sekamov Thank you!
Absolutely — that's exactly the workspace flow
1. You (as the owner) purchase the channels you need.
2. Via the API you create a user and get a unique URL for channel connection.
3. Your customer follows that URL to complete OAuth and connect their channel — generating a unique channel ID.
4. Your agent then uses that channel ID + your owner API key to post.
All connected channels draw from your main channel quota, so your customers don't need their own subscriptions.
Guide: https://docs.publora.com/guides/workspace