−20%

Annual plan discount

Save
New · Pubshr MCP

Stop leaving the chat to ship social posts

Connect Pubshr MCP once. Then schedule crossposts, list channels, and approve drafts from Cursor, Claude, or any MCP client — in the same conversation where the idea appeared.

Dream outcome: idea in an AI chat → pick a slot across all channels → review → publish — without distraction or tab-switching.

OAuth 2.1 — no API key in git Works with Cursor, Claude, VS Code… Nothing goes live without your OK

~5 min

from URL to first tool call

6 tools

channels, schedule, approve…

100%

posts need approve first

Start free — connect MCP See how to connect

Free plan · OAuth in minutes · Approve before publish

The real cost

The idea dies in the tab switch

You already wrote the post with AI. Then you open five dashboards — and momentum is gone.

Context switching tax

Copy from chat → paste into scheduler → pick channels → set time → repeat for every network. Every hop loses intent.

Tool sprawl

One app for drafting, another for scheduling, a third for approvals. Your “content stack” is a maze.

Fear of rogue AI posts

Teams avoid automation because one bad publish burns trust. Without a hard approve gate, nobody ships from chat.

Value equation

More outcome. Less time & effort.

People buy when the dream is big, success feels likely, and delay + sacrifice are small.

↑ Dream outcome ↑

Post from the AI you already use — crosspost, triage the queue, ship — without leaving the conversation.

↑ Likelihood ↑

Same Pubshr account, same channels, same calendar. OAuth + pending_approval mean the agent acts as you, safely.

↓ Time delay ↓

Paste /mcp, authorize once, ask “show my channels.” First crosspost in the same session.

↓ Effort ↓

No API keys in repos. No second dashboard for day-to-day. One URL. One consent.

What you get

The full stack in one connection

Not another “AI wrapper” — remote MCP into your real publishing system.

  1. 1
    Remote MCP server

    HTTP endpoint at /mcp for Cursor, Claude, VS Code Copilot, Windsurf, and other remote MCP clients.

    Replaces manual dashboard hops
  2. 2
    Six production tools

    list_channels, get_provider_schema, schedule_post, list_posts, approve_post, delete_post.

    A full content day from chat
  3. 3
    Native crossposting

    One schedule_post can hit multiple channel IDs. Check limits with get_provider_schema first.

    Replaces three web forms
  4. 4
    Brand-safe approval loop

    New posts land in pending_approval. Live only after you (or an explicit approve command).

    Zero “AI went rogue” risk
  5. 5
    Copy-paste client configs

    Pick your client below — JSON / CLI ready. OAuth does the rest.

    Minutes, not an integration project
  6. 6
    Start on Free

    Account + channel + authorize MCP. Feel the win before you upgrade.

    Risk reversal built in

Risk reversal. Worst case of a bad prompt is a draft stuck in pending_approval — not a live embarrassment. You keep the kill switch: approve or delete.

Same dashboard

Posts from chat still land in Pubshr Audience

MCP schedules into your real account. Followers, reach, reactions — the Audience KPIs you already know on the homepage stay the source of truth after publish.

Pubshr available in ChatGPT

Audience

Audience KPIs across connected channels · demo data

24.8K

Followers

+12.4%

186K

Reach

+8.1%

4.2K

Reactions

+15.2%

6.4%

Engagement rate

+0.8%
Setup

Connect your MCP client

Pick a client, copy the config, authorize once. Pubshr uses OAuth — no secret in the JSON.

Authentication: OAuth 2.1. Your client discovers Pubshr, opens consent, stores the token.

Client

After you paste the config

1

Authorize in the browser

Sign in to Pubshr and approve access. The token stays in the client.

2

Connect a channel in Pubshr

MCP does not create social logins. Connect Telegram / LinkedIn / X once in the web app.

3

Verify with one prompt

Ask: “Show my Pubshr channels.” Empty list → finish step 2.

Proof in prompts

Two workflows that pay for the setup

Crosspost one idea

«Check my Pubshr channels. Schedule tomorrow 11:00 Europe/Moscow on Telegram and LinkedIn: “Tomorrow at 19:00 we cover autoposting via MCP.” Check get_provider_schema first.»

Morning approval queue

«Show Pubshr posts with pending_approval. Summarize each. Approve those without typos and with a future publish time.»

FAQ

Quick answers

Do I need an API key?

No. Pubshr MCP uses OAuth 2.1. You authorize in the browser; the client stores the token.

Can the agent publish without me?

Scheduled posts land in pending_approval. They go live only after approve_post (you or an explicit command).

Which clients work?

Any remote MCP client that supports HTTP + OAuth — Cursor, Claude, VS Code Copilot, Windsurf, Codex, Gemini CLI, and more.

Is there a deeper setup guide?

Yes — the product blog has a step-by-step MCP guide with flow diagrams and tips.

Read the MCP setup guide

Get the outcome today

Create a free account, connect a channel, paste /mcp, authorize once — ship the first crosspost from chat.

Start free — connect MCP

Free plan · Minutes to connect · Approve before publish

We use cookies

We use cookies to improve your experience on our platform, analyze site traffic, and personalize content. By continuing to use our site, you consent to our use of cookies. Learn more in our Privacy Policy