SimplePost is a platform for AI agents, apps, and humans to post on social media. It gives you one TypeScript-powered posting layer and five ways to use it: SDK, HTTP API, Scheduler app, CLI, and MCP server.
SimplePost is open source and ownership first: get the code, run it yourself, modify it, and connect it to your own social platform apps and credentials. Learn more at simplepost.social.
| Interface | Best for | Docs |
|---|---|---|
| TypeScript SDK | Apps and agents that can call TypeScript directly | docs/typescript-sdk |
| HTTP API server | Non-TypeScript services, microservices, backend workers | docs/http-server |
| Scheduler app | Human writing, previewing, posting, and scheduling | docs/scheduler-app |
| CLI | Terminal workflows, scripts, CI jobs, local coding agents | docs/cli |
| MCP server | ChatGPT, Claude, Cursor, and other MCP-compatible AI clients | docs/mcp-server |
All five paths are backed by @simple-post/sdk, so they share the same platform model and posting behavior.
npm install @simple-post/sdkimport { post } from "@simple-post/sdk";
const results = await post({
content: {
text: "Hello from SimplePost",
media: [{ type: "image", url: "https://cdn.example.com/image.jpg" }],
},
platforms: ["x", "telegram", "linkedin"],
});Set up platform credentials with the platform guides in the public docs directory, or use the hosted Scheduler app / CLI account connection flows when you do not want to manage raw tokens directly. The repository is open source and can be run today.
Social APIs are inconsistent. Authentication, media rules, rate limits, scheduling behavior, and error responses all vary by platform. SimplePost hides that complexity behind one modern interface while still giving you access to the underlying code.
The main use cases are:
- AI agents that can validate, publish, or schedule social posts for a user.
- Product backends that need one posting interface instead of ten platform integrations.
- Humans who want a web UI for composing, previewing, and scheduling.
- Scripts and command line workflows that need reliable non-interactive posting.
- Self-hosted teams that want ownership, no subscription dependency, and no vendor lock-in.
| Platform | SDK publisher | Docs |
|---|---|---|
| X | Yes | X |
| Telegram | Yes | Telegram |
| Yes | ||
| Yes | ||
| Threads | Yes | Threads |
| TikTok | Yes | TikTok |
| YouTube | Yes | YouTube |
| Yes | ||
| Yes | ||
| Bluesky | Yes | Bluesky |
| DEV/Forem | Yes | DEV/Forem |
| Path | Purpose |
|---|---|
sdk/ |
Core TypeScript SDK and platform publishers |
server/ |
HTTP API server around the SDK |
scheduler/ |
Web scheduler app, account connections, API routes, and MCP server |
cli/ |
Command line posting tool |
examples/ |
SDK examples by platform |
docs/ |
Product and integration documentation |
Start with docs/README.md. It routes you to the interface you need and explains the common posting model shared by the SDK, server, app, CLI, and MCP server.
Release and compatibility references:
Found a bug or have a feature request? Open an issue or start a thread in Discussions.
See CONTRIBUTING.md for how to set up the repo and submit changes, and SECURITY.md for reporting vulnerabilities.
Everything in this repository is licensed under the MIT License.