capx café
For the builders.
And what comes next.
Create, schedule, and publish X posts from the coding agent that already understands your work.
Every post guarded. Your X token stays on the server.
The AI writes; casserole decides what ships.
Open source. Self-hostable. Yours to inspect.At home in
your agent
01 / From work to words
The commits. The late-night fixes. The small wins. Your agent has the context. Give it a way to turn that work into something worth sharing.
The change you shipped
fix: handle expired X access tokens refresh the token on the server retry the original send once keep credentials out of the client
You ask your agent
“Turn this token-refresh fix into a short build update. Keep it specific. Preview it before posting.”
Shipped a small fix for an annoying edge case: expired X tokens. capx café now refreshes the token on the server and retries the send once. The credential still never touches the agent.
Illustrative workflows based on capx café features. Nothing is posted from this page.
Try it with your own work02 / A little peace of mind
Give your agent a way to publish while keeping your X token on the server. Every post goes through casserole, capx café’s deterministic guardrail.
Look inside the security model
Real guardrail code, shown in a sandbox. X publishing is simulated.
Encrypted in the server vault. Your agent holds a short-lived session handle to request a post.
Six deterministic checks run at the publishing boundary. Calling the server directly still runs the guardrail.
The token is never decrypted for a blocked post. You can inspect the verdict and the audit trail.
Find the project
03 / Find your rhythm
24 skills help your agent find the words, plan the timing, and get your work out there. Start with the thing you just finished.
Turn a merged PR, a shipped feature, or a week of commits into a clear update.
Find a stronger opening, reshape a long read, and review the draft before it goes out.
Plan a cadence, keep your queue topped up, and see what has already shipped.
Use your image and video tools, attach the result, or run capx café on your own server.
Your agent supplies the intelligence. capx café supplies the publishing tools and guardrails.
Queue your posts, close your laptop, and get back to what you do best. Scheduled posts run on the server.
Find your flow04 / Pull up a chair
Add capx café to your coding agent. Connect your X account. Try a draft from something you’ve built.
Run these two commands inside Claude Code. The plugin includes the MCP server and capx café skills.
/plugin marketplace add vb-tyagi/capx-cafe /plugin install capx-cafe@capx-cafe
Then / Make the connection
Set your server URL, allowed email, and X app client ID using the configuration guide. Ask your agent to “connect my X account” and follow the browser authorization.
Next / Try something real
Ask your agent to draft a post from your work and run it through the guardrail. A preview doesn’t publish anything to X.
Look at my latest commit. Draft one specific X post about what changed and why it matters. Preview it through capx café, and show me the draft and verdict before publishing.
Before you settle in
The developer BYO lane is free on capx café’s side. You bring your own X developer app and pay X directly for API usage. Self-hosting also involves your own infrastructure costs. The creator lane will be a separate paid beta.
capx café runs as a stdio MCP server. Claude Code, Cursor, Codex, Windsurf, Cline, and other compatible MCP clients can use its tools. Claude Code has a bundled plugin; the repository includes skill adapters for Cursor, Codex, and Windsurf. Docker Desktop works through capx café’s custom MCP catalog.
Your coding agent uses the context you give it. The capx café service receives the post text you route through its publishing tools; it does not receive general access to your repository, files, or other apps. Your agent’s own privacy settings still apply. See what the service can and cannot see.
Yes. Queued posting loops run on the server. Your agent prepares the posts; the server publishes them on schedule, subject to guardrails and account eligibility. Loops require a verified X account that is at least 30 days old. Universal safety limits are 10 posts/hour and 40/day.
casserole applies deterministic checks for eligibility, rate limits, text quality, authenticity, kill-switch state, and audit. A post may pass, need a rewrite, be held, or be blocked. It checks caption text; attached images and videos are not content-moderated. Read the full security model and its limits.
Yes. The server is open source under AGPL-3.0; the client and skills use MIT. You can run the server with your own X app, database, keys, and domain. Read the self-hosting guide.
A creator lane using capx café’s X app is coming as a paid beta. Join the waitlist for access when it opens.
Planned beta: Short $5/mo · Tall $15/mo · Grande $35/mo. Compare options and costs