Three ways to connect
PostSider supports three integration patterns. Choose the one that best matches your agent’s runtime and your team’s tooling.MCP Server
A developer tool for AI agents. The repository ships
@postsider/mcp, exposing 17 tools. Build it from source yourself; it is not on npm and has no dashboard page. Configure both the API key and instance URL for Claude Code, Claude Desktop, Codex, or any MCP runtime.REST API
Versioned
/public/v1 endpoints for any HTTP client. Authenticate with an API key in the Authorization header and call endpoints from scripts, CI pipelines, or custom agents.SDK
The
@postsider/node npm package wraps the REST API with full TypeScript types. Install it in any Node.js project for the fastest programmatic path to publishing.What agents can do with PostSider
Once connected, your agent has the same publishing surface you have in the dashboard:- Publish, schedule, or draft posts across one or more connected channels in a single call
- Find the next free queue slot for a channel (UTC) so scheduling respects your posting plan
- List posts in a date range to review the content calendar
- Validate a post per channel before publishing, then fix whatever is flagged
- Change a post’s status or delete a post as your plan evolves
- Upload images and video from a public URL into the media library, then attach them to a post
- List connected channels and channel groups to get the ids every other call needs
- Pull analytics at the post and channel level, where the platform supports it
- Read notifications, such as publish failures or channels that need reconnecting
You need a PostSider API key to authenticate any Agent Bridge request. Generate one in the dashboard under Settings → API. See the Authentication page for full details.

