About PostSider
PostSider MCP gives AI agents selected API access to a social media calendar for content teams and agencies. It supports channel reads, draft preparation, and scheduling while keeping approval of live content with people.
Key features
- 01View channels, calendars, and queues
- 02Create, edit, and schedule posts
- 03Send drafts for human approval
- 04Manage media and content templates
- 05Check publishing status and analytics
- 06Connect to cloud or self-hosted instances
Use cases
- 01Review the social calendar for the next two weeks
- 02Prepare a draft for a selected channel
- 03Investigate publishing errors and fix post details
- 04Review channels and analytics across clients
MCP support
The MCP server exposes selected read and write operations from the PostSider public API. Clients authenticate with an organization API key and can connect to cloud or self-hosted instances, with separate scopes for reading, content changes, and channel administration.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @postsider/mcpPOSTSIDER_API_KEYSecretOrganization API key from PostSider under Settings -> API.POSTSIDER_API_URLInstance base URL. Defaults to https://api.postsider.com and must be HTTPS for non-local hosts.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
19Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project README@postsider/mcp
MCP (Model Context Protocol) server that gives AI agents selected access to a
PostSider instance through its public API. Works with Claude Code, Claude
Desktop, Codex, Cursor, and any MCP-compatible client. Talks to cloud
(api.postsider.com) or a self-hosted instance, authenticated with an
organization API key.
PostSider is a shared operational calendar: the agent prepares and schedules work, and a human reviews what actually goes live.
Install
1. Create an API key
In PostSider, open Settings -> API and generate an organization API key.
2. Connect your client
Claude Code:
claude mcp add postsider -e POSTSIDER_API_KEY=your_api_key -- npx -y @postsider/mcp
Claude Desktop or any generic MCP client:
{
"mcpServers": {
"postsider": {
"command": "npx",
"args": ["-y", "@postsider/mcp"],
"env": {
"POSTSIDER_API_KEY": "your_api_key"
}
}
}
}
3. Verify with a read-only prompt
Ask your agent, and confirm it answers without changing anything:
List my connected PostSider channels. Do not create or modify anything.
Then:
Show my PostSider calendar for the next 14 days. Do not create or modify anything.
4. Only then prepare a draft
Create one draft only for the selected channel. Show me the exact content first. Do not publish it.
From source
pnpm --filter @postsider/mcp build
Then point your client at the built entrypoint:
{
"mcpServers": {
"postsider": {
"command": "node",
"args": ["/absolute/path/to/apps/mcp/dist/index.js"],
"env": {
"POSTSIDER_API_KEY": "your_api_key",
"POSTSIDER_API_URL": "https://api.postsider.com"
}
}
}
}
Claude Code plugin
The package directory is also a Claude Code plugin: .claude-plugin/plugin.json
declares the API key as a secret user setting, .mcp.json starts this server at
the pinned released version, and skills/ contains focused workflows for calendar
review, content publishing, approvals, analytics, and agency operations. The
repository root is a plugin marketplace, so the plugin installs from the
repository directly:
Skill budget is full (5/5). The remote server advertises the skills it bundles through OpenAI's skills extension, which supports at most 5. All five slots are taken, so adding a new skill requires retiring or merging an existing one (
loadSkillCatalogfails closed above 5).
claude plugin marketplace add lumizone/postsider
claude plugin install postsider@postsider
Installation stores the key outside the plugin: pass it at install time with
--config api_key=your_api_key, or set it afterwards with
/plugin configure postsider@postsider inside Claude Code. The key is never
written into the plugin directory.
What the agent can do
37 tools (38 on the local stdio server), all prefixed postsider_.
Read
| Tool | Action |
|---|---|
postsider_list_channels | List connected social channels (ids, names, platforms). Call this first to get channel ids. |
postsider_get_agency_overview | Org-wide overview: clients, channels, queued, drafts, published, errors, pending approvals. |
postsider_get_customer_report | The same report scoped to one customer. |
postsider_list_groups | List channel groups. |
postsider_list_media | Browse the media library (paged, searchable) to reuse files already uploaded. |
postsider_get_channel_rules | Platform rules, max length and required settings schema for one channel. Call before posting to a new channel. |
postsider_get_queue_plan | A channel's recurring posting slots and timezone. |
postsider_get_smart_slots | Best upcoming times to post on a channel, avoiding booked slots. |
postsider_get_content_library | Saved hashtag groups, caption templates and UTM presets. |
postsider_find_slot | Next free queue slot for a channel, in UTC. |
postsider_list_posts | List posts in a date range, filterable by state (e.g. ERROR) and channel, paged. |
postsider_get_post | Full post details, including the publish error if any. |
postsider_get_post_missing_fields | Per-channel validation problems, so they can be fixed before publishing. |
postsider_get_post_analytics | Analytics for a single post. |
postsider_get_channel_analytics | Account-level analytics for a channel. |
postsider_get_notifications | Recent notifications: publish failures, channels needing reconnection. |
postsider_get_publishing_state | Whether publishing is active or paused for the organization. |
postsider_get_approval_status | Approval status of a draft, including a reviewer note when rejected. |
Write
| Tool | Action | Risk |
|---|---|---|
postsider_create_post | Create a post as a draft, a scheduled post, or an immediate publish across channels. | Creates content and can publish |
postsider_update_post | Edit an existing post in place: text, media, date, settings, first comment. Not for published or pending-approval posts. | Changes content, re-arms a scheduled post |
postsider_update_post_status | Move a post between draft and schedule. | Reversible |
postsider_request_approval | Send a draft into the human approval queue. | Reversible |
postsider_upload_media_from_url | Import media into the library from a public HTTPS URL. | Creates media |
postsider_upload_media_base64 | Upload an image or MP4 you hold as bytes (base64: 25 MB on the local server, 2.5 MB over the remote connection). No public URL needed. | Creates media |
postsider_upload_media_from_file | Local stdio server only. Upload an image or video (jpg, png, gif, webp, avif, bmp, tiff, mp4, mov, webm, mkv; up to 500 MB) from a file path on your own machine. Other file types are refused before being read. | Creates media |
postsider_connect_channel | Get the sign-in link to connect or reconnect a social account (the user approves it on the platform). Needs channels:write. | Starts a connection |
postsider_set_channel_enabled | Switch a channel on or off. Needs channels:write and an admin role. | Reversible |
postsider_disconnect_channel | Disconnect a channel; unpublished posts become drafts. Needs channels:write. | Destructive |
postsider_set_queue_plan | Replace a channel's posting slots ({time, days?}: minutes from midnight, optional weekdays 0-6). Read the plan first, it is replaced whole. Needs channels:write and an admin role. | Replaces settings |
postsider_set_channel_customer | Assign a channel to a client by name. Needs channels:write and an admin role. | Reversible |
postsider_save_library_item | Create or update a hashtag group, caption template or UTM preset. | Creates content |
postsider_delete_library_item | Delete a library item. | Destructive |
postsider_duplicate_post | Copy a post as a new draft, optionally onto another channel. | Creates a draft |
postsider_check_post | AI check of draft text for up to 3 platforms (uses the monthly AI allowance). | Uses AI quota |
postsider_rewrite_post | AI rewrites of a text in a chosen tone (uses the monthly AI allowance). | Uses AI quota |
postsider_delete_media | Delete a media file from the library and storage. | Destructive |
postsider_delete_post | Permanently delete a post and every other channel version of it (one group). Read the post first. | Destructive |
postsider_pause_publishing | Emergency stop for the whole organization. Resuming is human-only. | Destructive |
Access scopes (remote server)
| Scope | Allows |
|---|---|
posts:read | Every read tool. |
posts:write | Posts, media, library, duplication and AI checks. |
channels:write | Connecting, enabling, disabling, re-timing, re-assigning and disconnecting channels. Granted separately so an agent that may only schedule posts cannot reconfigure the workspace. Connections made before this scope existed need to be reconnected to get it. |
Billing, team and roles, API keys, MFA, account deletion and resuming a paused workspace are deliberately not available to agents; they stay in the dashboard.
Every tool declares readOnlyHint, destructiveHint, idempotentHint and
openWorldHint explicitly, so a client can tell a read from a kill switch.
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
POSTSIDER_API_KEY | yes | - | Organization API key (Settings -> API) |
POSTSIDER_API_URL | no | https://api.postsider.com | Instance base URL |
POSTSIDER_API_URL must be HTTPS. Plain HTTP is accepted only on loopback
(localhost, 127.0.0.1, [::1]) for local development.
For a self-hosted instance, point POSTSIDER_API_URL at where the public API is
served. Behind the bundled nginx the API lives under /api, so use your domain
plus /api, e.g. https://social.example.com/api. The server appends
/public/v1 to whatever you set.
Safety
- The API key is read from the environment and sent only to the configured PostSider API URL. It is never printed, logged, or included in an error.
- Credentials embedded in
POSTSIDER_API_URLare rejected. - Redirects are refused rather than followed: a redirect would move an authenticated request off the configured origin, so the client fails with an actionable message instead.
- Requests time out after 30 seconds, and a failing response body is read up to 8 KB before being reported.
- Tool arguments are validated locally, before any network call: ids must be
non-empty, dates must be real ISO 8601 dates (
2026-02-30is refused, not sent to the API), post statusdraftorschedule, and media imports require a public HTTPS URL. - A missing API key exits 1 with an explanatory message on stderr. stdout carries protocol frames only.
Development
pnpm --filter @postsider/mcp typecheck
pnpm --filter @postsider/mcp typecheck:tests
pnpm --filter @postsider/mcp test
pnpm --filter @postsider/mcp build
pnpm --filter @postsider/mcp version:gate
pnpm --filter @postsider/mcp validate:registry
pnpm --filter @postsider/mcp smoke:tarball
claude plugin validate --strict apps/mcp
Design
This server is a thin wrapper over selected /public/v1 REST API endpoints,
authenticated with the raw API key. It has no dependency on the backend and
pulls in only @modelcontextprotocol/sdk and zod, so it stays lean and easy to
maintain. All tool registrations live in a single factory, so the stdio
transport today and any future transport share one agent-facing surface.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.