CASE STUDY · PUBLIC
switchpost
Social posting infrastructure that runs on your own hardware: one Rust binary, 26 platforms, and three interfaces into one engine, with an MCP surface of 389 countable tools.
Status ruling active development
Evidence for Essay 5, Ideal tooling infrastructure: choosing and building tools. The spec names what that argument has to hit and the figures it will cite.
Problem
Social tooling for agents is either a rented SaaS with per-seat pricing or a bundle of per-platform scripts with no shared engine. The operation needed one binary that owns the whole posting surface.
Build
- One Rust binary with a SQLite store: no Docker, no Redis, no Postgres, the same native-binary discipline the $20 host forced.
- Three interfaces into one engine: a CLI for shell and agent use, a REST API with a real-time dashboard, and an MCP server for Claude, Cursor and Codex.
- Platform tiers declared in source (src/social/tier.rs): 12 Tier-1 and 14 Tier-2, with tier membership as the single source of truth for what is registered.
Outcome
- 389 MCP tool registrations, every one greppable in a single public file (src/mcp/mod.rs), grouped into 44 per-surface modules. Tool names carry provider prefixes rather than the project name, so relocating the repository cannot break an agent's integration.
- The product renamed itself Switchpost in-repo while the GitHub repository keeps the name social-forge; the register and this study use each name where each surface uses it. The September figures (300+ tools, 42 modules) are superseded in R23.
Provenance
| MCP tool registrations | 389 | #[tool( attribute count in src/mcp/mod.rs, 2026-10-26 |
|---|---|---|
| Tool modules | 44 | tools_*.rs file count in src/mcp/ |
| Platforms | 26 (12 Tier-1, 14 Tier-2) | tier declarations in src/social/tier.rs |
Reproduce
Clone the repository and count the registrations yourself, or run the server: the README publishes a one-command MCP start. The tier file and the registration file are both public, so every figure on this page is independently re-derivable.
https://github.com/ishan-parihar/social-forge
Published documents
From the documentation
26 platform targets are matched exactly, because several registered provider names are prefixes of others and a prefix match would double-draft to two platforms at once.
platforms-and-cli.md at 00a3109 (2026-10-25)
Every environment variable has a default, so nothing is required to start, and the SQLite-only rule is enforced at startup rather than discovered later.
deployment.md at 00a3109 (2026-10-25)
Deployment is one binary with a SQLite store, which is the whole reason the self-hosting story is credible: there is no managed service to wait on.
deployment.md at 00a3109 (2026-10-25)
The port consistency requirement between APP_URL and serve --port is documented with the exact 403 it produces, which is the shape of a document written by someone who hit the failure.
deployment.md at 00a3109 (2026-10-25)