PostSider MCP: hosted OAuth and local setup

PostSider makes the same social publishing workspace available to compatible AI agents over Model Context Protocol (MCP). Instead of connecting your agent to every social network directly, connect the channels in PostSider once, then let the agent work through a shared calendar and channel-level publishing status.

Start with the MCP quickstart to connect a client, list real channels, save exactly one draft and read it back. This is the recommended first run.

Which MCP connection should I choose?

	Hosted MCP	Local MCP
Endpoint	`https://mcp.postsider.com/mcp`	`npx -y @postsider/mcp`
Transport	Streamable HTTP	stdio
Authentication	OAuth through the client	Organization key in `POSTSIDER_API_KEY`
Install Node.js	Not required	Required
Tools	37	38, including local-file upload
Best for	OAuth-capable remote clients	Terminal agents and local workflows

The hosted MCP service is operated by PostSider. Do not put API keys in a remote URL. Use the OAuth sign-in flow. Local stdio reads a key from the process environment. The current package source version is 1.1.0; examples use the package name without pinning an older release.

Hosted connection

Claude Code
Codex
Cursor

claude mcp add --transport http postsider https://mcp.postsider.com/mcp

codex mcp add postsider --url https://mcp.postsider.com/mcp

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "postsider": {
      "url": "https://mcp.postsider.com/mcp"
    }
  }
}

After configuring the server, authorize PostSider in the client’s OAuth flow and first ask it to list your connected channels without modifying anything. A client without remote MCP OAuth support must use an appropriate local MCP transport or another supported integration path.

Local installation

Generate a key in PostSider Settings → API. On your own machine, use a compatible MCP client’s local configuration:

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

For Claude Code:

claude mcp add postsider -e POSTSIDER_API_KEY=YOUR_API_KEY -- npx -y @postsider/mcp

Never commit the key or expose it in frontend JavaScript. If using the local package against your own self-hosted instance, set POSTSIDER_API_URL to the correct API origin (behind the bundled reverse proxy, that usually includes /api). The default targets https://api.postsider.com.

First-run workflow

Connect one social channel

In the PostSider dashboard open Channels and connect one account. Prefer a test channel if available.

Verify with a read-only tool

Ask postsider_list_channels for real channel IDs, names and platforms. Do not guess identifiers.

Read platform rules

Use postsider_get_channel_rules for the selected channel before creating a post.

Save a draft only

Ask for a proposed caption, confirm it, then call postsider_create_post with type=draft for exactly one chosen channel. Do not schedule or publish.

Read the saved post back

Use postsider_get_post and the ID returned by creation. Verify the content, channel and state in both the tool result and dashboard.

Instructions such as “wait for my approval” are not enforced permission boundaries. Keep MCP client confirmations enabled. Local organization API keys have broad organization access. Hosted OAuth uses declared scopes including posts:read, posts:write and channels:write; actions are still subject to member roles and service rules. Formal PostSider team approval workflows are available from the Team plan upward.

Available tools

The current server implements 37 remote tools and 38 local tools. The extra local tool can upload a file from the computer running stdio; a hosted server cannot access files on your device. The current reference covers channels, content library, queue slots, media, publishing, analytics, approvals and emergency pause. See the complete tools reference for descriptions and risk categories. You can also inspect the tool schemas exposed by your connected MCP client. Use the current schema when exact parameters differ across releases.

More ways to build

Agent quickstart — complete first-run and readback guide
Authentication — key versus OAuth, security and limits
REST API — programmatic publishing without MCP
Node SDK — typed client for the supported public-API subset
Visual developer quickstart — client selector and runnable examples

Overview

MCP Server

REST API

SDK

PostSider MCP: hosted OAuth and local setup

Which MCP connection should I choose?

Hosted connection

Local installation

First-run workflow

Available tools

More ways to build

​Which MCP connection should I choose?

​Hosted connection

​Local installation

​First-run workflow

​Available tools

​More ways to build

Which MCP connection should I choose?

Hosted connection

Local installation

First-run workflow

Available tools

More ways to build