MCP Server
Expose social publishing as named tools that compatible AI clients can discover and call directly.
- Agent-native tool discovery
- No browser automation
- Works beside the human calendar
Developer platform
One social publishing layer for apps, automations and AI agents.
Schedule posts, work with connected channels and build publishing workflows through REST, MCP or an SDK instead of maintaining a separate integration for every social network.
Looking specifically for the API? See the social media scheduling API overview.
Three integration layers
Pick the interface that matches the caller.
The same publishing system can be driven by an agent, raw HTTP or typed application code.
REST API
Call the publishing layer directly from your backend, automation, cron job or internal tool.
- Predictable JSON over HTTP
- Schedule posts programmatically
- OpenAPI documentation
SDKs
Use the official TypeScript and Node.js client, or generate another client from the OpenAPI specification.
- Typed application code
- Autocomplete and helpers
- Same API underneath
Why a unified layer
Build the workflow once instead of rebuilding it per network.
One integration surface
Keep your application pointed at one publishing layer instead of maintaining separate social APIs, auth flows and request shapes in your own codebase.
Human and machine in one system
Your team can review the calendar while scripts and agents use the API underneath it. You do not need a separate automation-only product.
30+ publishing destinations
Use the same PostSider account for mainstream social networks, video platforms, communities and publishing destinations already supported by the product.
Scale from script to product
Start with curl, move to the SDK when the codebase grows, or let an AI client drive the same workflow over MCP.
Webhooks when you need them
Pro and Ultimate include webhooks for event-driven workflows where polling the publishing state is no longer enough.
Keep the operational UI
The API does not replace the dashboard. Humans can still inspect schedules, approvals and publishing state when a workflow needs intervention.
Claude via PostSider MCP
Create me a post for Instagram with this photo. On it. Drafted an Instagram post with your photo and queued it for Tuesday at 12:00.
For your AI agent
Give your agent the keys.
Connect any MCP agent and let it draft, schedule and publish for you. Or call the REST API and SDKs directly. No per-platform glue code, ever.
- Connect any MCP agent in one step
- Typed REST API and SDKs
- One integration, every network
- Same secure auth for humans and agents
+ any MCP agent Common builds
What developers use the publishing layer for.
Product release automation
Turn a deployment, changelog entry or release event into scheduled social posts without opening another dashboard.
See the workflow →AI social media agents
Let an external agent draft, schedule and inspect publishing actions over MCP instead of clicking through a UI.
See the agent setup →Internal publishing tools
Keep your own workflow and UI while using PostSider as the layer that connects it to the social platforms.
How to choose an API →Developer guides
Start with the interface, then go deeper.
Schedule posts with a social media API Auth, scheduling, UTC timestamps, publishing state and webhooks with concrete API shapes. Read guide → MCP vs REST vs SDK Choose the right interface based on whether the caller is an agent, backend or typed application. Read comparison → What is an MCP server? A practical explanation of agent tool calling and why a social publishing tool exposes MCP. Read guide →
API access from the first plan
You do not need an enterprise contract to start building.
REST API, MCP server and SDK access are included across the current PostSider tiers. Webhooks start on Pro.
StandardAPI · MCP · SDK
TeamAPI · MCP · SDK
ProAPI · MCP · SDK · Webhooks
UltimateAPI · MCP · SDK · Webhooks
FAQ
PostSider API, MCP and SDK.
What is the PostSider social media API?
PostSider exposes a REST API for programmatic social publishing, channel management and analytics. It lets your backend, script or automation use the same publishing system as the PostSider web app.
Can I schedule social media posts through the API?
Yes. You can create scheduled posts programmatically by sending the target channel, content and publish time to the PostSider API. The API reference documents the current request and response shapes.
Does PostSider support MCP for AI agents?
Yes. PostSider exposes publishing actions through a Model Context Protocol server so compatible AI clients can discover and call social publishing tools without driving the human dashboard.
Is there an SDK?
Yes. PostSider provides an official TypeScript and Node.js client. An OpenAPI specification is also available for teams that want to generate clients for other languages.
Which PostSider plans include API and MCP access?
The current Standard, Team, Pro and Ultimate plans include REST API, MCP server and SDK access. Webhooks are available on Pro and Ultimate.
When should I use MCP instead of REST?
Use MCP when an AI agent is the caller and should discover available actions. Use REST when your application or script already knows exactly which request it needs to make. Use the SDK when you want typed helpers around the REST API in a supported language.