SOCIAL MCP

Agentic founder-led distribution.

Your AI-native founding team is already in Claude, Codex, or another MCP client. Give it the social operations to research, publish, engage, and build relationships across LinkedIn and X.

ONE PROTOCOL

MCP

TWO PLATFORMS

LinkedIn + X

YOUR OPERATOR

Your agent

THE SURFACE

Four jobs. One agent context.

01 / RESEARCH

See the context before you act.

Read profiles, posts, networks, conversations, and account context. Search people and posts, then let your agent turn the raw material into a point of view.

ASK YOUR AGENT

Find founders in my network who engaged with my last three posts. Tell me what they are working on.

02 / PUBLISH

Turn a decision into a post.

Draft from the research, review the result in your agent, then publish to LinkedIn or X when you are ready. There is no separate content calendar to operate.

ASK YOUR AGENT

Turn the three strongest customer objections from this week into a short LinkedIn post.

03 / ENGAGE

Stay close to the conversation.

Read comments and reactions on the posts that matter. Your agent can prepare replies or react through the same account-aware social context.

ASK YOUR AGENT

Read the comments on my launch post. Draft thoughtful replies to the five questions I should answer today.

04 / RELATIONSHIPS

Work the people, not a generic list.

Research the person behind a signal, inspect the thread, and prepare or send messages and connection requests through your real social accounts.

ASK YOUR AGENT

Who should I reconnect with before our beta launch? Draft a personal note for each and wait for my approval.

THE DIFFERENCE

Infinitely customizable. Have your agent build it for you.

MCP is the connection standard, not the set of actions your agent gets. Social exposes social work directly, so your general-purpose agent can combine reads and writes around the way you actually distribute.

Learn how MCP works ↗
SURFACEWHAT THE MCP CONTROLSBEST FOR
Campaign MCPsCampaigns, sequences, senders, and campaign-workspace objects.Teams running a defined outbound motion.
Publishing MCPsContent queues, schedules, and publishing workflows.Teams with a planned publishing operation.
Scraping MCPsJobs, Actors, runs, and datasets.Operators assembling data collection and processing pipelines.
Social MCPAccount-aware social reads and writes across LinkedIn and X.Founders who want their general-purpose agent to build the workflow around the work.

YOU STAY IN CHARGE

Your agent operates. You decide what goes live.

Social starts with read access. Write tools appear only when you grant the matching write scope, and they act on the connected account immediately. Keep the confirmation moment in your MCP client for posts, replies, messages, and connection requests.

Need the account boundary in more detail? Read the LinkedIn account safety guide. Deciding between agent-led distribution and a predefined outbound workflow? Start with LinkedIn automation alternatives.

Cyrus NourooziCyrus NourooziUpdated

INSTALL

Two minutes. Then it works for you forever.

Pick your agent, follow along, send it one prompt. Your agent takes it from there.

1SettingsConnectorsAdd custom connector, then paste mcp.usesocial.dev
2Send Claude a prompt — it connects your accounts with you: