How do I install PostSider?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does PostSider need an API key?

The publisher lists these environment variables: POSTSIDER_API_KEY, POSTSIDER_API_URL.

What transport does PostSider use?

PostSider runs locally over stdio.

When was PostSider last checked?

Last checked 2026-11-09. Social media calendar for AI agents: read channels, create drafts, request approval.

PostSider MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @postsider/[email protected]

Credentials from the publisher

POSTSIDER_API_KEY — Organization API key from PostSider under Settings -> API.
POSTSIDER_API_URL — Instance base URL. Defaults to https://api.postsider.com and must be HTTPS for non-local hosts.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1POSTSIDER_API_KEY=<secret> POSTSIDER_API_URL=<value> claude mcp add io.github.lumizone-postsider -- npx -y @postsider/mcp@1.0.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.lumizone-postsider": {4      "command": "npx",5      "args": [6        "-y",7        "@postsider/[email protected]"8      ],9      "env": {10        "POSTSIDER_API_KEY": "<secret>",11        "POSTSIDER_API_URL": "<value>"12      }13    }14  }15}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.0.0
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

What is PostSider?

PostSider is an open-source social media management and scheduling platform built around four ways of working:

Use PostSider as	What you get
Social media scheduler	One calendar for planning, composing, approving, scheduling, and publishing content
Self-hosted platform	A Docker-based deployment you can run on your own infrastructure
Automation backend	A public REST API plus the `@postsider/node` SDK
AI-agent bridge	An MCP server that lets compatible agents work with PostSider through structured tools

PostSider ships with 33 active connectors registered in the application. You configure credentials only for the platforms you actually use.

AI features are optional. PostSider works without an OpenAI API key.

Quick Start

For a local evaluation, the fastest path is Docker Compose.

Requirements

Docker
Docker Compose

Start PostSider

git clone https://github.com/lumizone/postsider.git
cd postsider
docker compose up -d

The default Compose stack pulls:

ghcr.io/lumizone/postsider-app:latest

and starts PostSider with PostgreSQL, Redis, and Temporal.

Open:

http://localhost:4007

Create the first administrator account:

docker exec -it postsider pnpm bootstrap

The bootstrap command prints a one-time password. Sign in with:

[email protected]

and the generated password. PostSider then prompts you to set your real email address and password.

The root docker-compose.yaml is convenient for local evaluation. For an internet-facing deployment, use the production setup and the self-hosting guide.

Highlights

Scheduling and publishing

Visual calendar with drag-and-drop scheduling
Posting queue and find-free-slot scheduling
Smart Slot suggestions
Evergreen content recycling
Per-platform previews
Per-platform validation before publishing
Automatic first comments where supported
Bulk CSV import

Content workflow

Hashtag groups
Caption templates
Reusable snippets
UTM builder
Draft and approval workflows
Shared media library

Teams and organizations

Multi-organization workspaces
Separate workspaces for brands or clients
Admin and User roles
Shared publishing workflow

Automation

Public REST API
Node.js SDK: @postsider/node
MCP server: @postsider/mcp
Webhooks
Programmatic scheduling and channel access

Optional AI

Post Checker
Caption rewriting
Platform-level OPENAI_API_KEY
Per-organization bring-your-own key support

Security

Optional TOTP two-factor authentication
One-time recovery codes
Organization-wide 2FA enforcement
Encrypted provider credentials at rest
Security activity trail
Secure httpOnly cookies
CORS and CSP controls
Rate limiting
Server-side authorization and plan enforcement

Supported Platforms

The list below mirrors the active providers registered in:

libraries/nestjs-libraries/src/integrations/integration.manager.ts

Category	Platforms
Social & creator platforms	X, LinkedIn Profile, LinkedIn Page, Facebook, Instagram via Facebook, Instagram Standalone, Threads, YouTube, TikTok, Pinterest, Bluesky, Mastodon, Nostr, Farcaster, Lemmy, Twitch, Dribbble, Google Business Profile, Whop, Moltbook
Chat & community	Discord, Slack, Telegram
Blogs & publishing	Dev.to, Hashnode, Medium, WordPress, Ghost, Blogger, Notion, Mataroa, Write.as, Listmonk

That is 33 active connectors in the current integration registry.

You only need OAuth/API credentials for the providers you intend to use. See:

Mastodon supports custom instances through the standard Mastodon provider.

Adding a provider

Provider integrations live in:

libraries/nestjs-libraries/src/integrations/social/

A new connector typically:

Extends SocialAbstract
Implements SocialProvider
Is registered in socialIntegrationList in integration.manager.ts
Adds the corresponding frontend platform metadata/assets

New provider integrations are especially welcome as pull requests.

AI Agents (MCP)

PostSider includes an MCP server for compatible AI clients and agents.

The package is:

@postsider/mcp

The MCP layer is a thin interface over PostSider's public API and exposes 19 tools for workflows such as:

Listing connected channels
Reviewing the publishing calendar
Creating drafts
Requesting approval
Uploading media
Working with scheduled content
Reading analytics

The intended workflow is read-first and draft-first: an agent can prepare work inside the same PostSider workflow used by humans, while publishing remains a deliberate action.

Build the MCP server

pnpm --filter @postsider/mcp build

For a local/stdio connection, configure:

POSTSIDER_API_KEY
POSTSIDER_API_URL

POSTSIDER_API_URL points the MCP server at the PostSider instance you want to use.

Full MCP documentation:

Claude Code plugin

This repository also contains the Claude Code plugin metadata and the postsider-workflow skill.

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

A safe read-only connection check:

List my connected PostSider channels. Do not create or modify anything.

Public API & SDK

PostSider exposes a public REST API for external applications and automation.

Authenticate with your organization's API key.

Node.js SDK

The published SDK package is:

npm install @postsider/node

Example:

import Postsider from '@postsider/node';

const client = new Postsider(
  'your-api-key',
  'https://your-instance.com'
);

// Schedule a post
await client.post({
  type: 'schedule',
  date: '2025-01-15T10:00:00',
  posts: [
    {
      integration: { id: 'channel-id' },
      value: [{ content: 'Hello!' }],
    },
  ],
});

// List posts
const posts = await client.postList({
  page: 0,
  limit: 20,
});

// List connected channels
const channels = await client.integrations();

The public API is exposed under /public/v1.

Architecture

PostSider is a TypeScript pnpm monorepo.

postsider/
├── apps/
│   ├── backend/          # NestJS REST API
│   ├── orchestrator/     # Temporal workers
│   ├── frontend/         # Next.js dashboard
│   ├── commands/         # CLI/bootstrap utilities
│   ├── sdk/              # @postsider/node
│   └── mcp/              # @postsider/mcp
├── libraries/
│   ├── nestjs-libraries/ # Shared backend, database, integrations
│   └── helpers/          # Shared utilities
├── docker-compose.yaml
├── docker-compose.production.yaml
└── .env.example

Tech stack

Layer	Technology
Backend API	NestJS 11, TypeScript
Frontend	Next.js 15, React 19
Database	PostgreSQL + Prisma 6.5
Cache	Redis
Workflow engine	Temporal
AI	OpenAI, optional
Billing	Polar.sh, optional
Storage	Local filesystem, Cloudflare R2, or MinIO
Authentication	JWT, GitHub OAuth, Google OAuth, Generic OIDC
Monitoring	Sentry

Design decisions

Temporal for durable scheduling

Scheduled publishing and token-refresh work run through Temporal workflows so background jobs are not tied to one web-process lifetime.

Provider-based integrations

Each social platform is implemented behind a common provider interface. The active registry lives in integration.manager.ts.

Public API first

External tools can use /public/v1, while Node.js consumers can use @postsider/node.

One codebase for hosted and self-hosted deployments

Optional capabilities are controlled through environment configuration. Billing and AI are not required for a self-hosted installation.

Configuration

Start from the example environment file:

cp .env.example .env

The primary local-development settings are:

Variable	Purpose
`DATABASE_URL`	PostgreSQL connection string
`REDIS_URL`	Redis connection string
`JWT_SECRET`	JWT signing secret
`BACKEND_URL`	URL used to reach the backend
`FRONTEND_URL`	URL used to reach the frontend
`NEXT_PUBLIC_BACKEND_URL`	Public backend URL embedded in the frontend
`BACKEND_INTERNAL_URL`	Backend URL used by internal services

For production, set a dedicated ENCRYPTION_KEY as documented in .env.example.

The full reference is maintained in:

Storage

Local storage is the default:

STORAGE_PROVIDER=local
UPLOAD_DIRECTORY=./uploads

Cloudflare R2 and MinIO are also supported through environment configuration.

Provider credentials

Social providers have their own API/OAuth settings. You do not need to configure all 33 providers.

Configure only the services you plan to connect.

Self-Hosting

PostSider is designed to run on your own infrastructure.

Two Compose files are included:

File	Purpose
`docker-compose.yaml`	Simple local/evaluation stack using the published GHCR image
`docker-compose.production.yaml`	Production-oriented stack built from the repository

The production stack includes the PostSider application, PostgreSQL, Redis, MinIO, Temporal, and supporting services used by the deployment.

For production, use the dedicated guide:

Self-host PostSider

The production Compose file intentionally expects production secrets and deployment-specific values rather than shipping usable defaults.

Local Development

Requirements

Node.js >=20.17.0 <23.0.0
pnpm 10.6.x
PostgreSQL
Redis

Clone and install:

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

Create your environment file:

cp .env.example .env

Apply database migrations:

pnpm prisma-migrate-deploy

Create the initial admin:

pnpm bootstrap

Start the backend and orchestrator:

pnpm dev

In another terminal, start the frontend:

pnpm dev:frontend

Default development URLs:

Backend:  http://localhost:3000
Frontend: http://localhost:4200

Useful commands

# Backend only
pnpm dev:backend

# Orchestrator only
pnpm dev:orchestrator

# Frontend only
pnpm dev:frontend

# Generate Prisma client
pnpm prisma-generate

# Create a Prisma migration
pnpm prisma-migrate-dev

# Apply migrations
pnpm prisma-migrate-deploy

# Build backend + orchestrator
pnpm build

# Build the Node.js SDK
pnpm build:sdk

Contributing

Contributions are welcome.

Good places to contribute include:

New provider integrations
Bug fixes with clear reproduction steps
Documentation
Performance improvements
Automated tests
Type-safety improvements

Typical workflow:

git checkout -b feature/my-feature
# make changes
pnpm run build:backend

Then open a pull request with a clear explanation of the change.

For provider-specific contribution steps, see CONTRIBUTING.md.

Roadmap

Support PostSider

If PostSider is useful to you, consider starring the repository. It helps other developers discover the project. Bug reports, feature requests, and pull requests are also appreciated.

License

PostSider is licensed under the GNU Affero General Public License v3.0.

You may use, modify, and distribute PostSider under the terms of the AGPL-3.0. If you run a modified version as a network service, the license requires the corresponding source code to be made available to users of that service.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install PostSider?

Does PostSider need an API key?

What transport does PostSider use?

When was PostSider last checked?

Documentation

What is PostSider?

Quick Start

Requirements

Start PostSider

Highlights

Scheduling and publishing

Content workflow

Teams and organizations

Automation

Optional AI

Security

Supported Platforms

Adding a provider

AI Agents (MCP)

Build the MCP server

Claude Code plugin

Public API & SDK

Node.js SDK

Architecture

Tech stack

Design decisions

Configuration

Storage

Provider credentials

Self-Hosting

Local Development

Requirements

Useful commands

Contributing

Roadmap

Support PostSider

License