
Mcp Social
Let your coding agent list social channels, draft posts, and schedule or publish multi-platform updates through Postiz without leaving the terminal.
Overview
mcp-social is an MCP server for the Grow phase that lets AI agents manage Postiz channels and schedule or publish multi-platform social posts.
What is this MCP server?
- Connects AI agents to Postiz for multi-platform social posting
- Manage channels and publish or schedule posts from MCP tool calls
- Stdio npm package @infoinlet/mcp-social v0.1.1 for Claude Code–style hosts
- Suited to agent-driven launch threads, changelogs, and weekly content batches
- Part of the infoinlet marketplace services/mcp-social subfolder on GitHub
- Server version 0.1.1
- stdio transport
What problem does it solve?
Switching between your agent session and separate social schedulers breaks flow when you want the agent to ship posts as part of shipping features.
Who is it for?
Indie builders who already use Postiz and want Claude or Cursor to draft and queue social updates alongside code changes.
Skip if: Teams that need deep social listening, paid ad workflows, or posting without a Postiz account.
What do I get? / Deliverables
Your agent can list channels and schedule or publish posts through Postiz from one MCP registration.
- Registered stdio MCP server pointing at Postiz
- Agent-callable flows to list channels and schedule or publish posts
- Repeatable social publishing without manual dashboard context switching
Recommended MCP Servers
Journey fit
Sustained posting and channel management sit in Grow, where solo builders compound attention after the product exists. Content is the subphase for creating and pushing social copy on a cadence, which this MCP wires directly into Postiz.
How it compares
Postiz MCP integration for agents, not a standalone copywriting skill or SEO playbook.
Common Questions / FAQ
Who is mcp-social for?
Solo builders and small teams who use Postiz and want their AI coding agent to handle channel-aware scheduling and publishing via MCP.
When should I use mcp-social?
Use it during Grow when you are batching launch threads, changelog posts, or recurring social content and want the agent to call Postiz tools directly.
How do I add mcp-social to my agent?
Install the npm package @infoinlet/mcp-social, configure stdio transport in your MCP client, and connect it with valid Postiz credentials per the marketplace repo services/mcp-social docs.