Skip to content
Mehdi Messaoudene
Publishing tool · personal use2026in local testing

SocialPlug

Prepare, schedule and publish on social networks, without any public action ever leaving without your approval.

Where it started

Posting on several networks, answering messages and automating part of the work exposes two risks: content going out by mistake, and account credentials lying around in clear. Plugging an assistant into these tools makes the first risk worse.

What was built

A personal dashboard with drafts, variants, calendar, media and inbox, and an 86-tool MCP server to drive it from an assistant. Every public action requires a one-time confirmation, and account tokens are encrypted. All eight work packages are built; no real account is connected yet.

Results

86
MCP tools
8
work packages built
10 min
confirmation validity
5
failed logins before lockout

From the interface down to the data

  1. 01

    Dashboard

    Composer, calendar, per-network variants, media, inbox and contacts. Personal login with revocable sessions.

  2. 02

    Shared services

    The same services serve the dashboard and the MCP tools: preview, confirmation, scheduling, publishing. One rule, two entry points.

  3. 03

    Publishing queue

    pg-boss on PostgreSQL, separate process managed by pm2: revisions, transactional locks, controlled resume, session maintenance.

  4. 04

    Networks and relays

    Telegram, Bluesky, Facebook, Instagram, WhatsApp. A signed relay for Meta callbacks, whose contracts and signatures are tested; it is not deployed.

Engineering decisions

The choices worth defending, and why.

  • 01

    A frozen, one-time confirmation

    Before any public action, the tool builds a canonical preview, computes its fingerprint and asks for a confirmation valid for ten minutes, once only. If the content changes between preview and confirmation, the confirmation no longer counts. Actions requested by an assistant go through the same check.

  • 02

    Encrypted tokens, bound to their use

    Account tokens are stored in a versioned AES-GCM envelope, bound to the account and the use. No token appears in clear in the database. Integration credentials entered in the dashboard follow the same rule: the interface never receives their value.

  • 03

    An uncertain delivery is reviewed, not replayed

    When you do not know whether a message went out, resending risks a public duplicate. The queue flags these deliveries as uncertain and submits them for review instead of retrying blindly.

  • 04

    Automations that know when to stop

    Paced sends deduplicate messages, respect the 24-hour window, freeze the audience at the start and stop as soon as a reply arrives. In testing, providers are simulated: no real public action has been executed.

Tech stack

  • TypeScript
  • PostgreSQL 16
  • Prisma
  • pg-boss
  • MCP
  • pm2
  • Cloudflare Worker

Other projects