MCP (Model Context Protocol) lets an AI client talk to your tools and data. Pubshr ships its own MCP server: after OAuth, an agent can list your channels, schedule posts, approve moderation, and delete drafts — on your behalf.
Below is a short setup guide plus two scenarios that already cover day-to-day SMM and content-team work.
Visual
How it works — in plain words
No protocol jargon needed. Remember the chain: you type in chat → AI asks Pubshr → Pubshr acts on your channels.
Diagram 1. The big picture
Diagram 2. One request, step by step
Diagram 3. Safe publishing loop
At a glance
- →Web endpoint: /mcp with OAuth 2.1
- →Tools:
list_channels,schedule_post,approve_post, and more - →Scheduled posts land in pending_approval — they publish only after approve
- →Works with Cursor, Claude Desktop, and other remote MCP clients
Context
What Pubshr MCP can do
The server runs in your Pubshr account context. The agent only sees your channels and posts. Content is adapted to platform limits (Telegram, X, LinkedIn, Facebook, Instagram, Threads), and constraints are available via get_provider_schema.
-
list_channelsConnected channels with IDs and providers -
get_provider_schemaText/media limits and requirements for a platform -
schedule_postSchedule a post to one or many channels (crossposting) -
list_postsQueue and statuses (publish + approval) -
approve_postApprove a post from pending_approval -
delete_postDelete a scheduled post
Setup
Connect in 4 steps
You need a Pubshr account and an MCP client (e.g. Cursor). The endpoint and OAuth flow are already wired in the app.
Open MCP settings in your client
In Cursor: Settings → MCP. In Claude Desktop — Connectors / Custom MCP. Add a remote HTTP server.
Set the server URL
Use https://pubshr.com/mcp. The client discovers OAuth and prompts you to sign in to Pubshr.
Authorize access
Pubshr shows a consent screen in the browser. Approve the client — the token is stored by your MCP client.
Verify tools
Ask in chat: “Show my Pubshr channels” — the agent should call list_channels. If the list is empty, connect channels in the Pubshr web UI first.
{
"mcpServers": {
"pubshr": {
"url": "https://pubshr.com/mcp"
}
}
}Server name and exact JSON shape depend on the client version. What matters is https://pubshr.com/mcp and the OAuth flow your client starts.
Security. The token is bound to your user. Do not commit MCP configs with access tokens to public repos.
Scenario 1
Crosspost one idea to several networks
Classic job: announce a webinar on Telegram, LinkedIn, and X at once. Instead of three web forms, you describe the task to the agent.
«Check my Pubshr channels. Schedule a post for tomorrow at 11:00 Europe/Moscow on Telegram and LinkedIn: “Tomorrow at 19:00 we cover autoposting via MCP — link in bio.” Check limits with get_provider_schema first.»
What the agent does
- →list_channels — fetch channel IDs
- →get_provider_schema — verify text limits
- →schedule_post with multiple channel_ids — create the crosspost
- →Return a post ID in pending_approval
Nothing goes live until you (or the agent on your command) call approve_post. That keeps accidental drafts out of production.
Scenario 2
Morning approval queue
A content manager opens Cursor in the morning and asks to triage the approval queue: what is ready, what to reject, what to fix.
«Show Pubshr posts with approval status pending_approval. Summarize each. Approve those without typos and with a future publish time; leave the rest.»
What the agent does
- →list_posts filtered by pending_approval
- →Summarize content and channels
- →approve_post for selected IDs
- →Optionally delete_post for clear junk
Moderation becomes a conversation instead of table clicks — especially when auto-strategies and AI generation fill the queue in Pubshr.
Practice
Useful habits
Channels first
Without channels connected in the web UI, list_channels is empty — MCP does not create social OAuth sessions for you.
Always check schema
Before a long X post or Instagram carousel, ask get_provider_schema so the agent hits fewer limit errors.
Approve explicitly
Avoid “publish everything now” without review. Keep the two-step loop: schedule → approve.
Timezones
Pass timezone in schedule_post (e.g. Europe/Moscow), otherwise times default to UTC.
Takeaway
Pubshr MCP moves scheduling and moderation into the AI chat you already use. Setup is /mcp plus authorization; then the agent uses your tools. Start with a crosspost and the morning approve queue — those two flows cover most daily routine.
Try Pubshr with MCP
Connect channels, add /mcp in your client, and run crossposting from chat.
Open PubshrAccount + OAuth — then tools are available to your agent