Social Neuron

Social Media MCP Connectors for AI Agents: Evidence-Checked Guide

Published · Updated · 11 min read

Which social media tools have MCP support?

As of 24 August 2026, current first-party pages verify MCP surfaces for Social Neuron, Postiz, Post Bridge, Typefully, and Hootsuite. These are verified examples, not an exhaustive market census. An MCP page proves that a vendor documents a connector. It does not prove that authentication, project selection, drafting, publishing, or analytics work for your account.

The best social media MCP connector is therefore not the one with the longest feature table. It is the one that can complete your exact job with the smallest permission set and return evidence you can inspect.

This comparison uses five public evidence states:

  1. Documented: a current first-party page describes the MCP surface.
  2. Verified: an independently inspectable public receipt proves the bounded operation completed.
  3. Not run: this review did not test the operation against an account.
  4. Not public: an internal check exists, but stage-level evidence is withheld and no named stage claim is made.
  5. Not established: the public evidence available for this review cannot support the claim.

If a cell does not have the evidence for one of those states, it stays unknown. Unknown is not the same as no.

The evidence-checked connector comparison

ConnectorCurrent first-party evidenceWhat that evidence supportsPublic review stateWhat remains unproven here
Social NeuronDeveloper surface, OpenAPI 3.1 spec, and live tool catalogThe full catalog (99 tools), with a narrower default discovery profile, covers OAuth 2.1 + PKCE and API key scopes (read, write, distribute, analytics, comments, and autopilot) for project selection, brand-context reads, content generation, scheduling, and analyticsDocumented public contract; internal stage-level run receipts are Not public, and nothing was publishedA buyer-run account receipt, reviewable saved-platform draft, destination publish receipt, audience response, and business outcome
PostizMCP introduction and tool referenceIts docs describe integrations, draft/schedule/immediate-publish operations, post listings and settings, and media toolsNot runAccount-specific authentication, platform delivery, failure handling, and external receipts
Post BridgeMCP setup and tool guideIts guide describes OAuth or API-key setup plus content, scheduling, media, and analytics operationsNot runAccount-specific permissions, destination state, retry behavior, and outcome lineage
TypefullyAI agents pageIts page describes MCP and Agent Skill paths for drafting, refinement, scheduling, publishing, feedback, and calendar workNot runAccount-specific scope, external receipts, analytics lineage, and failure behavior
HootsuiteMCP integration pageA current official MCP integration surface existsNot runThe usable tool boundary, account eligibility, write behavior, receipts, and outcomes

Sources were retrieved 24 August 2026, except the Upload-Post pricing page, retrieved 6 November 2026. The Social Neuron evaluation is a publisher disclosure, not an independently inspectable run receipt. Vendor pages can change. Recheck the exact source and your account entitlement before granting write access.

Verification map from a vendor page through account scope, internal artifact identity, destination receipt, and measured outcome
Verification map from a vendor page through account scope, internal artifact identity, destination receipt, and measured outcome

Compare the workflow, not the marketing nouns

MCP standardizes how a client and server exchange tools and context. It does not standardize product quality, account permissions, or proof that an external network accepted a post. A useful comparison follows the workflow from left to right.

1. Source receipt

Record the exact first-party page, retrieval date, and claim. A vendor homepage is not enough for a detailed capability, price, or platform claim. Link the setup or tool page that contains it.

2. Client and transport

Identify the client and connection type you will actually use. A connector can be documented and still fail because the client does not support the required transport, authentication flow, or tool approval model.

For protocol background, read what MCP means for content creators. For a repository-centered implementation, see the AI content pipeline with MCP.

3. Account and project identity

Name the exact brand, workspace, and destination account before any write. Multi-project ambiguity should stop the run. A successful response attached to the wrong project is not a success.

4. Permission boundary

Separate read, internal draft, schedule, publish, reply, and account-management permissions. Tool availability is not task approval. Start read-only, then allow one internal draft. Add an external action only through a new, specific approval.

5. Durable artifact identity

A reviewable draft needs an identifier or version you can bind to an approval. Generated text in a chat window is not enough. Store the source brief, project, platform, checks, and artifact identity together.

6. Destination receipt

An MCP tool saying done is not proof that a social network accepted the post. Require the destination identifier and, where practical, query external state before recording CONFIRMED. If the result is uncertain, use UNKNOWN and inspect before retrying.

7. Outcome lineage

Delivery is not performance. A case study needs the exact artifact, verified exposure, measurement window, denominator, attributable demand, and activation definition. Missing analytics is unavailable, not zero.

Use the product-neutral MCP connector verification worksheet to record these receipts before choosing a connector.

What the public Social Neuron evaluation summary establishes

Because Social Neuron is the publisher of this guide, we do not grade our own connector above third-party tools using private internal logs. Stage-level execution and storage details are not published as comparative proof:

Exact internal evaluation and storage details are intentionally withheld.

This keeps the comparison on a level playing field: a vendor comparison should not promote a documented capability to a completed workflow without an inspectable account receipt.

What the other official pages establish

Postiz

Postiz publishes a dedicated MCP introduction, client setup, examples, and a tool reference. The current introduction describes operations for listing integrations, drafting or scheduling posts, publishing immediately, reading post state, changing draft settings, and generating media. It also documents API-key and bearer-token connection paths.

We did not connect a Postiz account or run a post workflow. This page therefore marks the surface Documented and the execution Not run.

Post Bridge

Post Bridge publishes an MCP setup guide with OAuth and API-key paths. Its current guide covers content creation, scheduling, updates, deletion, media, and analytics retrieval. That makes it relevant when an agent needs a posting-oriented control surface.

We did not test account scope, platform delivery, or a destination receipt. Those states remain unknown here.

Typefully

Typefully's current AI-agents page describes both chat-based MCP access and an Agent Skill path. It documents drafting, refinement, feedback, calendar management, scheduling, and publishing.

We did not test those operations against an account. The page supports a documented-capability claim, not a delivery or outcome claim.

Hootsuite

Hootsuite publishes a current MCP integration page. This review verified that first-party surface but did not test its account eligibility, tool scope, or execution behavior. It remains in the comparison as a documented connector with a deliberately incomplete evidence row.

Best MCP Server for a Social Media Posting AI Agent

When an AI agent in Claude Desktop, Claude Code, ChatGPT, or Cursor needs to plan, generate, schedule, and inspect social media posts, the right MCP server depends on the job. We publish Social Neuron, so treat this as a map of documented surfaces, not a ranking:

AI Social Tools with an API or MCP Server for Claude and ChatGPT Agents

The table restates what the sources in this guide document. It does not rank the tools, and nothing in it was run against an account.

Tool / ConnectorDocumented accessDocumented operationsSource
Social Neuron MCPHosted Streamable HTTP, npm stdio, and REST OpenAPI 3.1; OAuth 2.1 + PKCE or API keysFull catalog (99 tools) with scoped read, write, distribute, analytics, comments, and autopilot accessDeveloper surface
Postiz MCPAPI key or bearer tokenListing integrations, drafting, scheduling, immediate publishing, post state, draft settings, and mediaMCP introduction, retrieved 24 August 2026
Post BridgeOAuth or API keyContent creation, scheduling, updates, deletion, media, and analytics retrievalMCP guide, retrieved 24 August 2026
TypefullyChat-based MCP and an Agent Skill pathDrafting, refinement, feedback, calendar management, scheduling, and publishingAI agents page, retrieved 24 August 2026
HootsuiteNot establishedNot establishedMCP integration page, retrieved 24 August 2026
Upload-PostNot establishedIts pricing page lists an MCP server among plan features; operations are not establishedPricing page, retrieved 6 November 2026

How to choose a social media MCP connector

Choose from your required job and evidence standard:

There is no universal winner in this evidence set. The decision changes with the job, client, account, required permission, and receipt standard.

Claims deliberately excluded

This refresh removes vendor price snapshots, exact tool totals, broad platform totals, model-family counts, unsupported exclusivity, and claims that analytics automatically become learning. Those claims expire quickly and were not needed to answer the reader's decision.

It also avoids ranking a connector from a homepage, a generated summary, or a community post. Community discussion can reveal demand. It does not verify a vendor capability.

A safe connector evaluation prompt

Use this before any external write:

Use only read tools for project [exact name]. Return the project identifier, current brand context, available analytics window, sources, and unavailable fields. Do not create, schedule, publish, reply, or alter an account. Stop if the project is ambiguous.

Then test one internal artifact:

Create one platform-targeted draft from approved brief [identifier]. Return the durable artifact identifier, project, platform lineage, checks, unresolved claims, and exact actions not taken. Do not schedule, publish, reply, or contact an external account. Reject the run if the identifier or platform lineage is missing.

Only after that path returns the required receipts should a separate approval name an exact artifact version, destination account, allowed action, and required destination receipt.

The verifier guide explains why the check should be independent of the system that produced the claim.

Limitations and falsifier

To avoid self-preferencing in a publisher-written roundup, Social Neuron's internal stage-level execution and storage details are intentionally withheld and treated as Not public alongside the third-party rows. The rows use dated first-party documentation and public discovery endpoints rather than hands-on comparative grading. No connector was tested here for audience response, signup, activation, revenue, retention, or causal lift.

Withdraw a vendor row if its cited first-party MCP page disappears or no longer supports the stated operation. Withdraw any recommendation if an account-scoped test cannot preserve project identity, permission state, artifact identity, or destination evidence.

Frequently asked questions

What is a social media MCP connector?

It is an MCP server that exposes social-media-related tools or context to an MCP client. The exact scope varies by vendor. Inspect the current tool schemas and permissions rather than assuming every connector can create, publish, and measure.

What is the best social media MCP server?

There is no universal winner. Choose the connector that completes your required workflow with the smallest permissions and returns durable internal and external receipts. Documentation is the first check, not the final proof.

Does a successful MCP call mean a post is live?

No. The call may have created internal state, submitted an external request, or returned before destination confirmation. Require a destination identifier and verify external state before recording CONFIRMED.

Did the Social Neuron test prove publishing works?

No external post was sent for this article — nothing was published, and stage-level results are not public. Use the read-only and single-draft evaluation prompts above in your own account before enabling distribution scopes.

Sources

Retrieved 24 August 2026:

Retrieved 6 November 2026:

Next step: Download the worksheet, test one read-only path, and inspect the receipt before comparing plans or granting write access.