Connect AI agents to PostSider via the MCP server tools

PostSider ships an MCP server, @postsider/mcp, that exposes 19 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 local stdio server that your MCP client launches. It is distributed as the npm package @postsider/mcp, it is not a dashboard page, and it is not hosted by PostSider Cloud. Your API key stays in your own MCP client config and is sent only to your PostSider instance. The server requires Node.js 20.17 or newer.

Before you start

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.

Pick a client

Connect Claude Code, Claude Desktop, Cursor, Codex, or any MCP-compatible client with the commands below. npx downloads the published package on first run, so there is nothing to clone or build.

Connect Claude Code

Use claude mcp add with npx and pass your key as an environment variable:

claude mcp add postsider -e POSTSIDER_API_KEY=your-api-key -- npx -y @postsider/mcp

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

Claude Code can also install the server as a plugin, which bundles a read-first, draft-first workflow skill:

claude plugin marketplace add lumizone/postsider
claude plugin install postsider@postsider

Pass the key at install time with --config api_key=your-api-key, or set it later with /plugin configure postsider@postsider.

Connect Codex

Codex — the CLI, the ChatGPT desktop app, and the IDE extension — share one MCP configuration. Register PostSider with codex mcp add and pass your key as an environment variable:

codex mcp add postsider --env POSTSIDER_API_KEY=your-api-key -- npx -y @postsider/mcp

Then start a new Codex session and ask it to “list my PostSider channels”. Run codex mcp list to confirm the server is registered, or /mcp inside the Codex TUI. In the ChatGPT desktop app and the IDE extension, open Settings → MCP servers → Add server, choose STDIO, and provide npx -y @postsider/mcp with the same environment variable.

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 npx:

{
  "mcpServers": {
    "postsider": {
      "command": "npx",
      "args": ["-y", "@postsider/mcp"],
      "env": {
        "POSTSIDER_API_KEY": "your-api-key"
      }
    }
  }
}

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`	No	`https://api.postsider.com`	Base URL of your PostSider instance

On PostSider Cloud the default is correct. On a self-hosted instance, the public API is served under /api behind the bundled nginx, so set POSTSIDER_API_URL to your domain plus /api, for example https://social.example.com/api. The server appends /public/v1 to whatever you set. Plain HTTP is accepted only on loopback (localhost, 127.0.0.1, [::1]).

Available tools

PostSider exposes 19 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_get_publishing_state`	Whether publishing is active or paused for the organization
`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 and every other channel version of it
`postsider_request_approval`	Request approval for a post
`postsider_get_approval_status`	Read approval status for a post
`postsider_pause_publishing`	Emergency stop for the organization: queued posts are held and new posts are refused. Resume is human-only

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

From source (optional)

To build the server from the repository instead of using the published package, clone it and build apps/mcp:

git clone https://github.com/lumizone/postsider.git
cd postsider
pnpm install
pnpm --filter @postsider/mcp build

Then point your client at apps/mcp/dist/index.js with node:

{
  "mcpServers": {
    "postsider": {
      "command": "node",
      "args": ["/absolute/path/to/apps/mcp/dist/index.js"],
      "env": {
        "POSTSIDER_API_KEY": "your-api-key"
      }
    }
  }
}

Overview

MCP Server

REST API

SDK

Connect AI agents to PostSider via the MCP server tools

Before you start

Connect Claude Code

Connect Codex

Connect Claude Desktop, Cursor, and other clients

Configuration

Available tools

From source (optional)

​Before you start

​Connect Claude Code

​Connect Codex

​Connect Claude Desktop, Cursor, and other clients

​Configuration

​Available tools

​From source (optional)

Before you start

Connect Claude Code

Connect Codex

Connect Claude Desktop, Cursor, and other clients

Configuration

Available tools

From source (optional)