KensaSocial Purchase →

Sovereignty Engineered.

[ Local-first social orchestration. Zero cloud telemetry. Absolute data ownership. ]

KensaSocial · MCP · v0.1.0

System Architecture

[ Technical specification — read sequentially ]

01

The Vault

Local SQLite

Drafts, queues, license keys, and OAuth tokens persist in kensa.db on your SSD. WAL mode enabled. No third-party dashboard holds your content hostage. The queue is yours — portable, inspectable, sovereign.

~/data/kensa.db · daemon · 60s poll

02

The Edge

Stateless Proxy

Cloud enters only at publish time. Our edge service validates your license and forwards the payload. We never store post content, OAuth tokens, or queue state in our infrastructure.

POST /dispatch · license gate · zero retention

03

The MCP

Agent Integration

Native Model Context Protocol over stdio. Cursor, Claude, Windsurf — your agent calls schedule_social_post and moves on. Four tools. One connection. Zero context switching.

schedule · list · cancel · status

Publication
Targets.

[ seven channels · one queue · schedule_social_post ]

01

Twitter / X

twitter

02

LinkedIn

linkedin

03

Threads

threads

04

Reddit

reddit

05

Discord

discord

06

Telegram

telegram

07

Bluesky

bluesky

Connect accounts via the local dashboard (localhost:3456) or kensasocial connect <platform>. Schedule posts from your IDE via MCP schedule_social_post. V1 ships one profile per license — multi-tenant orchestration is on the PRO roadmap.

Reddit posts require reddit_options · title + subreddit

Image platforms (Instagram, Facebook) — roadmap

Deployment
Protocol.

[ License first — not optional. Global install, CLI login, MCP wizard, then boot. Dashboard at localhost:3456 for queue inspection and OAuth. ]

$ npm install -g kensasocial
$ kensasocial login <KEY>
$ kensasocial install
$ kensasocial start

Need help?

Support channel.

Email [email protected] with your order email and the output of kensasocial doctor. Moving machines? Device transfer guide.

Output · kensasocial status · queue · prune

$ kensasocial status

KensaSocial Connection Status

Profile ID  6a417f0530a5d40851b1d4e5

Platform              Status
────────────────────────────────────────
Twitter / X           Connected
LinkedIn              Connected
Bluesky               Connected
Reddit                Disconnected
Discord               Disconnected
… threads · telegram

$ kensasocial connect bluesky
Opening browser for bluesky OAuth…

$ kensasocial queue
2 pending · 0 missed

$ kensasocial prune --dry-run
Would delete 3 published posts older than 14 days

$ kensasocial daemon start
Dispatch daemon running · 60s poll