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:
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.
# 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
GitHub Actions CI
Runtime image published to GHCR
Public REST API
Node.js SDK
MCP server
Broader automated coverage for core flows
Enable strictNullChecks across the codebase
Mobile app
Plugin system for custom integrations
Advanced analytics dashboard
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.
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.
P
Postsider
lumizone·13 个星标·
Open-source social media scheduling for 30+ platforms, with a public API, SDK and MCP server.