How to Connect PostEverywhere to Claude

Claude has quietly become the best writing partner in social media marketing. It holds a brand voice across a week of content, it edits without flattening your tone, and with Projects it remembers your style guide between sessions. Then you hit the wall every marketer knows: the writing is done, and now you have to carry it, post by post, into a scheduler.

Connect PostEverywhere to Claude and that wall disappears. Type this instead:

"Take the five captions we just wrote, adapt each one for its platform, and schedule them Monday to Friday at 10am across LinkedIn, Instagram and Threads."

Claude calls PostEverywhere, your posts land in the queue, and the whole workflow stays in one conversation.

The mechanism is a custom connector: Claude talks to remote Model Context Protocol (MCP) servers, the open standard Anthropic created and ChatGPT and Cursor later adopted. Point Claude at the PostEverywhere MCP server and it gains real capabilities: schedule posts, upload media, generate images, read analytics. Anthropic keeps investing here too. The MCP 2026-07-28 update landed in Claude this week, and the connectors directory now lists over 950 servers.

This guide shows exactly how to connect PostEverywhere to Claude, step by step. PostEverywhere runs the hosted MCP server that covers Instagram, LinkedIn, TikTok, YouTube, Facebook, X, Threads, Pinterest, Bluesky, Discord, Telegram and WordPress from one connection. It takes about two minutes, and unlike the ChatGPT version of this setup, there is no API key to copy anywhere.

Written by Jamie Partridge, Founder. Published 31 July 2026.

Check this first, or the button you need will not be there. On a Claude Team or Enterprise plan, only an Owner can add a custom connector. If there is no Add custom connector button, that is why: ask an Owner to add PostEverywhere under Organization settings, then start at Step 3 below. Free plans allow one custom connector, which is all this needs.

Table of Contents#

1. What you need to connect PostEverywhere to Claude
2. Why Claude works so well with the PostEverywhere connector
3. Step-by-step: add PostEverywhere as a Claude connector
4. PostEverywhere in Anthropic's Claude connector directory
5. Six PostEverywhere prompts to try in Claude
6. What Claude can actually do with your PostEverywhere accounts
7. PostEverywhere in Claude Desktop, mobile and Claude Code
8. Connect PostEverywhere to Claude or ChatGPT?
9. Limits, safety and troubleshooting the PostEverywhere connector
10. Connect PostEverywhere to your other assistants
11. FAQs

What you need to connect PostEverywhere to Claude#

Two things:

1. Any Claude plan. Custom connectors work on Free, Pro, Max, Team and Enterprise, per Anthropic's connector documentation. Free accounts are capped at one custom connector, which is fine here because one is all you need. This is a real difference from ChatGPT, where custom connectors require a paid plan. On Team and Enterprise, an owner adds the connector at the organisation level first, then each member connects their own account.

2. A PostEverywhere account. Every plan from Lite ($9/mo) includes the full API and the hosted MCP server; there is no separate developer tier. The 7-day free trial covers everything, so you can run this entire guide before paying anything. Once signed up, connect the social accounts you want Claude to publish to. All top platforms are included on every plan.

That is the whole list. No server to deploy, nothing to install, and, because Claude's connector flow uses browser sign-in, no API key to create or paste.

Want the fastest possible start? Start a 7-day free trial, connect two or three accounts, and have Claude scheduling before you finish this article. Card required, $0 charged today, cancel anytime.

Why Claude works so well with the PostEverywhere connector#

Anthropic proposed MCP in late 2024, so Claude has had longer than any other assistant to make tool use feel native. It shows in the numbers too: in our State of AI Agents in Social Media report, Claude accounts for 83% of AI assistant connections to PostEverywhere. Three things stand out once you connect a social publishing server.

Projects hold your brand voice. Put your style guide, banned words, sample posts and audience notes into a Project, and every scheduling conversation inside it writes in your voice before it ever calls a tool. Our guide to using Claude for social media writing covers this side in depth; the connector turns that writing into published posts without a copy-paste step.

Long context means whole-week planning. Claude comfortably holds a month of past posts, a content calendar and a set of drafts in one conversation, then schedules against all of it. Asking "what did we already post about pricing this month?" before queueing next week is a real workflow, not a demo.

Approval stays in your hands. Claude shows you each tool call before it runs. When it wants to schedule ten posts, you see the payloads and approve once or per action. That reviewability is the sane middle ground between hand-posting everything and full autopublish automation.

Under the hood, the PostEverywhere MCP server exposes 38 tools covering scheduling, publishing, media upload, AI image generation, account health, campaigns, webhooks and analytics. It talks to each platform's official API, which matters: your accounts stay compliant, and you never hand a password to a bot.

Step-by-step: add PostEverywhere as a Claude connector#

The flow is: add the connector, connect, approve, prompt. Screenshots of every step live on our MCP server page.

Step 1: Open Connectors under Customize#

In claude.ai, open Customize, then Connectors. It now lives under Customize, not Settings, which is where older guides still send you. Press the +, then Add custom connector. On Team and Enterprise this starts in Organization settings, then Connectors, done once by an Owner; members then see it under their own Connectors page.

Step 2: Paste the server URL#

Name the connector PostEverywhere and paste the server URL:

https://mcp.posteverywhere.ai

Leave the OAuth client ID and secret fields empty. The server handles sign-in itself.

Step 3: Connect and sign in#

Click Connect on the new connector card. A browser window opens on PostEverywhere's sign-in page. Log in with your normal account; this is the standard OAuth dance, the same as "Sign in with Google" anywhere else.

Step 4: Approve access#

Claude shows you what the connector can do before it can do anything: create and schedule posts, list accounts, upload media, generate captions and images, read analytics, manage campaigns and webhooks. Approve, and the connection mints a revocable key for you behind the scenes. Nothing to copy, nothing to store, and you can revoke it from your PostEverywhere dashboard at any time.

Step 5: Run a sanity check#

Start a new chat, enable the connector from the + menu at the lower left of the chat box, and ask:

"Show me my connected social accounts on PostEverywhere."

Claude calls the list_accounts tool and returns your linked platforms with their status. If you see your accounts, you are live. Total setup time is usually under two minutes.

PostEverywhere in Anthropic's Claude connector directory#

Our MCP server is listed in Anthropic's Claude connector directory, the reviewed catalogue of services Claude can operate. Listings are built and maintained by the developers behind each tool and published under Anthropic's own terms and review policy.

What the listing changes is discovery and trust, not capability. The server at https://mcp.posteverywhere.ai does exactly what it did before, and anyone who added it by URL already had everything. But you can now find PostEverywhere in Claude's own connector settings rather than needing the URL in advance, and inclusion means the server has been through Anthropic's review. For a tool you are handing publishing access to your brand accounts, that second point matters more than the first.

Six PostEverywhere prompts to try in Claude#

With PostEverywhere connected, plain language is now the interface. Some real prompts that map cleanly onto the tools:

1. The brand-voice batch.

"Using the voice guide in this Project, write and schedule three LinkedIn posts about our new analytics feature for Tuesday, Wednesday and Thursday at 9am."

2. The cross-platform adaptation.

"Take the draft above, produce an Instagram caption, an X post under 280 characters and a Threads version, and schedule all three for tomorrow morning."

This is cross-posting with per-platform rewrites, driven from one message.

3. The image-included post.

"Generate a clean product-style image of a desk with a content calendar on screen, attach it to the Instagram post, and schedule for Friday at noon."

4. The month review.

"Pull my post results for the last 30 days, tell me which three posts performed best, and draft two follow-ups in the same style."

5. The approval workflow.

"Draft next week's five posts, but save them all as drafts. Do not publish anything until I have reviewed them."

The connector has a draft mode built in for exactly this: Claude saves the posts unpublished, you review them in the dashboard (or ask Claude to list its drafts), and only approved drafts get scheduled. Pair it with our best time to post data when you pick the slots.

6. The cleanup.

"List everything scheduled for next week, and move anything on Saturday to Monday morning."

Rather see the tools before you connect? The MCP server page lists all 38 tools by group, with screenshots of every connection step and copy-paste configs for each client. Every plan from $9/mo includes the full set.

What Claude can actually do with your PostEverywhere accounts#

The PostEverywhere connector surface is the same 38-tool set every MCP client gets, enumerated in full on the MCP server page. In practice it groups into five jobs:

• Publish and schedule: single posts, bulk batches, cross-posted variants, drafts, retries for failed posts.
• Media: upload from a URL, generate images, attach media to posts.
• Accounts: list connections, check account health, spot expired tokens before they eat a scheduled post.
• Measure: post-level results and account analytics summaries.
• Orchestrate: campaigns, webhooks, caption generation for when you want the tool to write instead of Claude.

What it cannot do is act invisibly. Every write action surfaces as a tool call you can inspect, and the team workspace history shows what was created and when.

PostEverywhere in Claude Desktop, mobile and Claude Code#

The PostEverywhere connector follows your Claude account. Add it once on the web and it is available in Claude Desktop and the mobile apps as well, wherever connectors are enabled, so approving a Thursday post from your phone is genuinely possible.

If you work in a terminal or want an agent that runs unattended, Claude Code speaks the same protocol with one command:

claude mcp add --transport http posteverywhere \
  https://mcp.posteverywhere.ai \
  --header "Authorization: Bearer pe_live_YOUR_KEY"

That variant authenticates with an API key instead of browser sign-in, which suits scripts and scheduled agents. Developers building something bigger can drop to the REST API directly; it is the same surface the MCP server sits on.

Connect PostEverywhere to Claude or ChatGPT?#

Both work, and PostEverywhere connects to either. We publish the ChatGPT walkthrough as a sibling to this one. The honest differences:

• Plan gate. Claude allows custom connectors on the Free plan (one connector). ChatGPT requires Plus or higher with Developer Mode enabled, per OpenAI's documentation.
• Auth flow. Claude's flow is browser sign-in with a minted, revocable key. ChatGPT's asks you to paste an API key during connector setup.
• Writing. For long-form brand voice held across a week of content, Claude's Projects give it the edge. For quick one-off captions, they are close. Our ChatGPT vs Claude vs Perplexity comparison covers the writing side properly.

If you use both assistants, connect both. The connector is per-assistant, the PostEverywhere account is one, and the queue they publish into is shared. (Gemini users: the app cannot add custom connectors yet, but Gemini CLI and the Gemini API can.)

For the wider landscape of agent-operable schedulers, MCP support across vendors, and where each option fits, see our roundups of the best social media scheduling tools for AI agents and social media MCP servers compared.

Limits, safety and troubleshooting the PostEverywhere connector#

Claude asks before it acts. Tool calls need your approval, per conversation or per action depending on your settings. Keep approvals on while you build trust in the workflow; loosen them once the outputs are boringly reliable. If you want a deeper look at what agents should and should not do unsupervised, read what social media AI agents are.

Rate limits are the API's, not Claude's. The hosted server enforces the same per-key limits as the developer API: 60 requests a minute is far more than a scheduling conversation ever uses.

If the connector will not appear in a chat, check the + menu at the lower left and make sure it is toggled on for that conversation. On Team and Enterprise, confirm an owner has added it at the organisation level first.

If a scheduled post fails, ask Claude to run the retry tool, or check account health; the usual culprit is an expired platform token, and the fix is reconnecting the account in the dashboard.

It cannot post to Facebook Groups. Nobody can. Meta retired the Groups API on 22 April 2024 and removed the permission that let software publish to Groups, so this applies to every third-party tool. Our guide to Facebook Groups for business covers what still works.

The connector cannot exceed the tools it exposes. Approving it issues a revocable key scoped to your PostEverywhere account, not to the social platforms. It calls our 38 tools, and none of them can change your billing, delete your account or read your card details.

If you disconnect, revoke the key from your PostEverywhere dashboard as well. Belt and braces. Revoking does not disconnect your social accounts, and posts already scheduled still publish, because the queue is ours, not the assistant's.

Connect PostEverywhere to your other assistants#

PostEverywhere runs one hosted MCP server, so the same account and the same key drive every client. Only the setup step differs, which is why each assistant gets its own walkthrough:

They all publish into the same queue and the same content calendar, so running Claude for one workflow and ChatGPT for another against a single PostEverywhere workspace is normal, not a workaround. The full tool surface, and the patterns people build on top of it, are on the agents page.

FAQs#

What am I actually connecting Claude to?#

PostEverywhere. Claude has no social integrations of its own, so it never talks to Instagram or LinkedIn directly. The custom connector points Claude at the PostEverywhere MCP server, and PostEverywhere holds the authorised account connections and publishes through each platform's official API. Claude reasons, PostEverywhere publishes, the platform receives.

Can Claude really post to Instagram, TikTok and LinkedIn?#

Yes. Through the connector, Claude schedules and publishes to Instagram, TikTok, LinkedIn, Facebook, X, YouTube, Threads, Pinterest, Bluesky, Telegram, Discord and WordPress using each platform's official API. Nothing is scraped and no passwords are shared.

Do I need to know how to code?#

No. The entire setup is paste-a-URL, click Connect, sign in, approve. The Claude Code variant exists for developers, but the browser flow in this guide involves no code at all.

Which Claude plan do I need?#

Any of them. Custom connectors are available on Free, Pro, Max, Team and Enterprise; Free accounts can add one custom connector, which covers this setup. Team and Enterprise need an owner to add the connector for the organisation first.

Is PostEverywhere in Anthropic's Claude connector directory?#

Yes. Our MCP server is listed in Anthropic's Claude connector directory, so you can find it in Claude's connector settings instead of pasting the URL by hand. Adding it by URL still works exactly the same way.

Can Claude post to a Facebook Group through PostEverywhere?#

No, and neither can any other tool. Meta retired the Facebook Groups API in April 2024, so Group posts can only be made manually inside Facebook.

Is it safe to connect Claude to my social accounts?#

The connection uses browser sign-in and mints a scoped, revocable key; Claude never sees your social passwords, and PostEverywhere talks to each platform through its official API. Claude also shows you each action before it runs. Revoke access anytime from your dashboard.

Does this cost extra on the PostEverywhere side?#

No. The MCP server and full API are included on every plan, starting with Lite at $9/mo. The 7-day free trial includes everything; a card is required to start it, and you can cancel anytime during the trial.

Can Claude generate the images for my posts too?#

Yes. The connector includes an image generation tool, so "write the post, generate a matching image, schedule both" works as a single request. You can also use the AI image generator in the dashboard.

Can I use Claude and ChatGPT with the same account?#

Yes. Add the connector in Claude and in ChatGPT's Developer Mode separately; both publish into the same queue and calendar, so your team sees one schedule regardless of which assistant filled it.

What is the difference between this and Zapier?#

Zapier runs pre-built triggers between apps; you configure a workflow, then it repeats. A connector gives Claude open-ended tools it composes on the fly: draft, adapt, schedule, review, reschedule, all in conversation, with judgment applied at each step. For recurring fixed pipelines, automation wins; for anything you would otherwise do by hand in a scheduler, the conversation wins.

Wondering whether Claude should use MCP or you should script the API instead? API vs MCP settles it by use case.

Before connecting anything, it is worth two minutes on how to give an agent access safely: no passwords, approval on, kill switch known.

Comparing this against the other options? Our AI social media agents comparison ranks the field on setup effort and capability.