A Social Posting Queue with an Approval Gate
Internal tools · Industry page
We built and manage this under Dashworth. The repository name stays off this page.
The repository name is withheld. This page describes the capability: draft, then approve, then post.
No screenshot. The repository name and any connected accounts stay off this page.
The brief
An agent that can draft a post should not also be the thing that publishes it. The missing piece was an approval gate and a server other tools could call.
What Dashworth did
The system is a Model Context Protocol server for social posting. Drafts can be prepared from an agent workflow. A person approves them before they go out. Companion MCP servers in the same toolkit cover WordPress, voice synthesis, image generation, and media processing with FFmpeg.
A social API provider is one of the connectors. The exact networks are chosen per engagement. This page does not list accounts.
Deliverables
Stack. MCP · WordPress · FFmpeg
This is infrastructure for publishing, not a public content site, so it has no sitemap of its own in this write-up. The public content it can support is covered under the YouTube and social services.
Footer line for the client site: Social Media Systems by Dashworth.
Questions
What platform is the social posting system built on?
A Model Context Protocol server, with related servers for WordPress, voice, images, and media files. The repo name is not published here.
How was the posting system optimized for AI search?
It is a tool, not a marketing site. The pages it helps publish can carry schema and llms.txt. The server itself is not an SEO property.
Related work
The work stays with Dashworth.
Call or text 650-393-3378. We meet in Northeast Florida and San Mateo, and we take contract roles inside larger companies. No account managers, no handoffs.