Connect AI agents to PostSider via the MCP server tools

The PostSider repository ships an MCP server, @postsider/mcp, that exposes 17 tools over the public REST API. It implements the Model Context Protocol and runs locally over stdio. It works with PostSider Cloud or any self-hosted instance.

The MCP server is a developer tool you run yourself. It is not published to npm (npm install @postsider/mcp will not work), not available as a page in the dashboard, and not hosted by PostSider Cloud. To use it, clone the PostSider repository, build apps/mcp, and point your MCP client at the built entry point.

The server runs locally over stdio and your agent launches it. Your API key stays in your own MCP client config and is sent only to your PostSider instance.

Before you start

Clone the repository

git clone https://github.com/lumizone/postsider.git
cd postsider
pnpm install

Generate an API key

In the PostSider dashboard, go to Settings → API, and create an organization API key. Copy it now, it is shown once. See Authentication for details.

Build the server

The server lives in the repository under apps/mcp. Build it once:

pnpm --filter @postsider/mcp build

This produces apps/mcp/dist/index.js, the entry point your MCP client runs.

Connect Claude Code

Use the claude mcp add command, pointing it at the built server and passing your key and instance URL as environment variables:

claude mcp add postsider \
  --env POSTSIDER_API_KEY=your-api-key \
  --env POSTSIDER_API_URL=https://api.postsider.com \
  -- node /absolute/path/to/apps/mcp/dist/index.js

Restart Claude Code so it picks up the change, then ask it to “list my PostSider channels” to confirm the connection.

Connect Claude Desktop, Cursor, and other clients

Most MCP clients use the same JSON structure. Add PostSider under your client’s mcpServers key, running the server with node:

{
  "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"
      }
    }
  }
}

Configuration

The server is configured entirely through environment variables.

Variable	Required	Default	Description
`POSTSIDER_API_KEY`	Yes	(none)	Organization API key from Settings → API
`POSTSIDER_API_URL`	Yes	(none)	Base URL of your PostSider instance. Use `https://api.postsider.com` for Cloud or `https://social.example.com/api` for the bundled self-hosted proxy.

Set POSTSIDER_API_URL explicitly. On PostSider Cloud use https://api.postsider.com. On a self-hosted instance, the public API is served under /api behind the bundled nginx, so set it to your domain plus /api, for example https://social.example.com/api. The server appends /public/v1 to whatever you set.

Available tools

PostSider exposes 17 tools. See the Tools reference for full parameters and examples.

Tool	Description
`postsider_list_channels`	List connected channels with ids, names, and platforms
`postsider_get_agency_overview`	Get organization-wide operational counts and recent errors
`postsider_get_customer_report`	Get a customer-scoped agency report
`postsider_list_groups`	List channel groups
`postsider_find_slot`	Return the next free queue slot for a channel (UTC)
`postsider_list_posts`	List posts within a date range
`postsider_get_post_missing_fields`	Per-channel validation for a post before publishing
`postsider_get_post`	Get one post by id
`postsider_get_post_analytics`	Analytics for a single post
`postsider_get_channel_analytics`	Account-level analytics for a channel
`postsider_get_notifications`	Recent notifications, such as publish failures
`postsider_upload_media_from_url`	Import an image or video into the media library
`postsider_create_post`	Create, schedule, or publish a post across channels
`postsider_update_post_status`	Change a post’s status
`postsider_delete_post`	Delete a post
`postsider_request_approval`	Request approval for a post
`postsider_get_approval_status`	Read approval status for a post

Start every workflow with postsider_list_channels. The channel ids it returns are required by the scheduling, analytics, and posting tools.

Overview

MCP Server

REST API

SDK

Connect AI agents to PostSider via the MCP server tools

Before you start

Connect Claude Code

Connect Claude Desktop, Cursor, and other clients

Configuration

Available tools

​Before you start

​Connect Claude Code

​Connect Claude Desktop, Cursor, and other clients

​Configuration

​Available tools

Before you start

Connect Claude Code

Connect Claude Desktop, Cursor, and other clients

Configuration

Available tools