KensaSocial — Sovereignty Engineered.

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 / XBeta

twitter

02

03

Threads

threads

04

05

Bluesky

bluesky

06

Discord

discord

07

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.

X (Beta) — fair use applies; approximately 100 posts per calendar month for typical individual or small-team volume

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.

Frequently
Asked.

[ Practical answers — no engineering deep dives ]

What does kensasocial start do?: It boots the local dashboard (localhost:3456), spawns the background dispatch daemon, and runs the MCP server in your terminal. Your IDE connects to MCP while that session is open.
I pressed Ctrl+C — will posts still publish?: Yes. The dispatch daemon runs detached in the background. Ctrl+C stops the dashboard and MCP in that terminal, but scheduled posts keep publishing until you run kensasocial daemon stop.
How do I stop scheduled publishing?: Run kensasocial daemon stop. Check status with kensasocial daemon status or the dashboard header — Dispatch · Running / Dispatch · Stopped.
How do I connect social accounts?: CLI: kensasocial connect reddit (or twitter, linkedin, threads, bluesky, discord, telegram). Dashboard: open the Accounts tab and click Connect. Verify with kensasocial status.
How do I schedule posts from my IDE?: Run kensasocial install to register MCP with Cursor, VS Code, Claude Desktop, or Windsurf. Ask your agent to use schedule_social_post — drafts land in your local vault and publish when due.
How does the free trial work?: Launch is $39/month with a 7-day free trial, processed through Lemon Squeezy. Your license key arrives in the receipt email. Activate with kensasocial login <KEY>. Cancel anytime from your Lemon Squeezy customer area.
What is X (Beta) fair use?: Twitter/X publishing is a beta feature. It is intended for typical individual or small-team volume — approximately 100 posts per calendar month per license — not high-volume automation. See our Terms for details.
Something is not working — what should I run?: kensasocial doctor checks Node, your local vault, license activation, relay connectivity, dashboard, and dispatch daemon status. Email [email protected] with the output.
Where is my data stored?: Drafts, schedules, and settings live in a local SQLite file (kensa.db) on your machine — typically under ~/.kensasocial/ when installed globally. Nothing is synced to our cloud until a post is due to publish.

Output · status · doctor · daemon lifecycle


$ kensasocial status

KensaSocial Connection Status

Profile ID  6a417f0530a5d40851b1d4e5

Platform              Status
────────────────────────────────────────
Twitter / X           Connected
LinkedIn              Connected
Threads               Disconnected
Reddit                Disconnected
Bluesky               Connected
Discord               Disconnected
Telegram              Disconnected


$ kensasocial doctor
Node.js ............... OK
Dispatch daemon ....... Running
Dashboard ............. Running with API auth enabled

$ kensasocial daemon stop
Dispatch daemon stopped.

$ kensasocial queue
2 pending · 0 missed

$ kensasocial daemon start
Dispatch daemon running · 60s poll