# PostEverywhere Is Now a Claude Connector: What That Actually Means > Our MCP server is listed in Anthropic's Claude connector directory. Here is what a connector is, what changes for you, and what it still cannot do. **Source:** https://posteverywhere.ai/blog/posteverywhere-claude-connector **Author:** Jamie Partridge **Published:** 2026-08-16 --- **PostEverywhere's MCP server is now listed in Anthropic's Claude connector directory.** In practice that means Claude can schedule and publish to your social accounts without you installing anything, editing a config file, or copying an API key by hand. You add the connector, approve access, and ask for what you want in plain language. *Last updated: August 2026.* Announcement posts are usually the least useful thing a company publishes, so this one tries to be worth the read whether or not you use us: what a connector actually is, what changes, and the three things it still cannot do. *Written by Jamie Partridge, Founder of PostEverywhere.* ## What is a Claude connector? A connector is a service Claude can operate on your behalf, built on the [Model Context Protocol](https://code.claude.com/docs/en/mcp). MCP is an open standard that lets an assistant call another product's tools directly, rather than describing what you should go and click. [Anthropic's directory](https://claude.com/connectors) is the reviewed catalogue of those services. Listings are built and maintained by the developers behind each tool, and published to the directory under Anthropic's own terms and review policy. The practical difference is that a connector is something you switch on, not something you build. Our [comparison of the API and MCP surfaces](/blog/social-media-api-vs-mcp) covers when each one is the right choice. ## What changes now that we are listed? Less than the announcement implies, and that is the honest answer. Our server has been running at `https://mcp.posteverywhere.ai` for months, and anyone who added it manually already had everything it does. What the listing changes is discovery and trust. You can find the connector where you would expect to look, rather than needing to know our URL in advance, and inclusion means the server has been through Anthropic's review rather than being a URL you found in a blog post. For a tool you are handing publishing access to your brand accounts, that second point matters more than the first. > **Want to try it?** Add the connector, approve access, and ask Claude to schedule something. [Start a 7-day trial](/pricing). Card required, cancel any time. ## How do you add PostEverywhere to Claude? Three steps, and none of them involve a terminal: 1. Open your connector settings in Claude and choose to add one. 2. Paste `https://mcp.posteverywhere.ai`. There is no client ID and no secret to generate. 3. Approve access. This mints a revocable key rather than exposing a permanent credential. Claude Code adds the same server with a single command, and the [Claude Code walkthrough](/blog/how-to-use-posteverywhere-with-claude-code-mcp) covers that path. For the Claude Desktop route step by step, see [connecting Claude to social media](/blog/connect-claude-to-social-media). ## What can Claude actually do once it is connected? 33 tools across all 11 platforms we support: Instagram, LinkedIn, X, Facebook, TikTok, YouTube, Threads, Pinterest, [Bluesky](/bluesky-scheduler), [Telegram](/telegram-scheduler) and Discord. That covers drafting and scheduling posts, [adapting one post per network](/cross-posting), uploading media, generating captions and images, running campaigns, checking account health, and reading back analytics. You can ask for a week of posts, review what it proposes, and approve. The useful mental shift is that you stop operating a dashboard and start delegating an outcome. Our roundup of [AI agents for social media](/blog/best-ai-agents-for-social-media) covers where the rest of the category currently sits on that. ## Which other social tools have a Claude connector? Three social media tools run official MCP servers as of August 2026: PostEverywhere, [Metricool](https://metricool.com/social-media-management-with-claude/) and [Buffer](https://buffer.com/mcp), whose server shipped in May 2026. Ours is the deepest publishing surface of the three at 33 tools across 11 platforms. Metricool's strength is analytics rather than publishing, and Buffer's covers its own channel set. Hootsuite, Sprout Social, Publer, SocialPilot, Later and SocialBee have announced none. If you want the tool-by-tool detail rather than our summary of it, our [MCP servers comparison](/blog/social-media-mcp-servers) breaks down what each server exposes, and [nine agent routes ranked by setup steps](/blog/easiest-ai-agents-for-social-media-management) compares them on how much work connecting actually takes. ## What can it still not do? Three limits worth knowing before you rely on it. **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 without exception. Our guide to [Facebook Groups for business](/blog/facebook-groups-for-business) covers what still works. **It cannot publish to a network you have not connected.** The connector reaches the accounts already authorised inside PostEverywhere. An empty account list is almost always this, not a failed connection. **It does not remove the need to review.** Nothing publishes without your approval, which is deliberate. An assistant that can post to your brand accounts unsupervised is a liability, not a feature. > **Building rather than delegating?** The same capabilities are available over REST. See the [developer documentation](/developers) and the [social media API](/social-media-api). ## What access does the connector actually get? Worth being specific, because "let an AI post to my accounts" is a sentence that should give anyone pause. Approving the connector issues a **revocable key scoped to your PostEverywhere account**, not to the social platforms themselves. Claude never sees your Instagram password or your LinkedIn session. It calls our tools, and we publish through each platform's official API using the tokens you authorised when you connected those accounts. That indirection is the whole security argument for the [Model Context Protocol](https://modelcontextprotocol.io/) approach over browser automation. An assistant driving a logged-in browser has whatever access you have, with no audit trail and no way to revoke it short of changing your password. A tool layer has a fixed list of things it can do, a key you can revoke from your settings without touching any social account, and a record of what was called. Three practical consequences: - **Revoking is one click and does not disconnect your social accounts.** Kill the key, keep your integrations. - **The connector cannot exceed the tools it exposes.** There are 33 of them, and posting is one. It cannot change your billing, delete your account or read your card details, because no tool does those things. - **Scheduled posts still run if you disconnect Claude.** The queue is ours, not the assistant's. Our guide to [safe agent access](/blog/ai-agent-access-to-social-media) covers the permissions model in more depth. ## What should you ask it first? The failure mode with a new connector is asking for too much at once and not trusting the result. Three prompts that work well as a first session: **"What social accounts do I have connected?"** A read-only call that confirms the connection works and shows Claude what it is looking at, before anything is written. **"Draft three LinkedIn posts about [topic] and show me before scheduling."** This exercises generation and per-platform adaptation while keeping you in the approval loop. **"Schedule the second one for Tuesday at 9am."** The point where it stops being a chat and starts being an operator. From there the useful pattern is a weekly session: ask for a week of drafts, edit the two that need it, approve, and leave the queue to run. ## Does this cost extra? No. The MCP server is included on [every plan](/pricing), and plans start at $9 a month. There is no separate connector fee and no higher tier required to use it. We run a 7-day trial on every plan. A card is required to start it and there is no free plan, which is the honest trade-off against tools that offer a permanent free tier with narrower platform coverage. ## Where this sits in what we are building We have said for a while that the interesting shift in social media tooling is not better dashboards, it is not needing one. A listing in Anthropic's directory is a small step in that direction rather than the destination, and there is plenty we still want to do: deeper analytics through the connector, better campaign primitives, and more of the publishing surface exposed as tools rather than parameters. If you use it and something is missing or wrong, tell us. That feedback is considerably more useful to us than the announcement. ## FAQs ### What is a Claude connector? A connector is a service Claude can operate directly on your behalf, built on the Model Context Protocol. You authorise it once and then ask for what you want in plain language, rather than switching to another tool. ### Is PostEverywhere in Anthropic's connector directory? Yes. Our MCP server is listed in Anthropic's Claude connector directory, so Claude Code and Claude Desktop can add it without a manual configuration file. ### How do I add PostEverywhere to Claude? Open your connector settings, paste `https://mcp.posteverywhere.ai`, and approve access. There is no client ID or secret to generate, and approving creates a revocable key rather than a permanent credential. ### Does the Claude connector cost extra? No. It is included on every PostEverywhere plan, starting at $9 a month. There is no separate connector charge and no minimum tier. ### Which platforms can Claude publish to through PostEverywhere? All 11 we support: Instagram, LinkedIn, X, Facebook, TikTok, YouTube, Threads, Pinterest, Bluesky, Telegram and Discord. ### Can Claude post to a Facebook Group through the connector? 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. ### Will Claude publish without asking me first? No. Publishing goes through an approval step by design. An assistant with unsupervised access to your brand accounts is a risk rather than a convenience. ### Do I need to know how to code to use the Claude connector? No. The connector is a hosted URL you paste into your assistant's settings. Writing code is only necessary if you would rather build against our REST API instead.