capx café
Overview
Description from the maker (original English)
Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 48/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Marketing & social media
- You need to fill in: CAPX_CHOKEPOINT_URL, CAPX_EMAIL
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
CAPX_CHOKEPOINT_URL,CAPX_EMAIL,CAPX_LANE,X_CLIENT_ID
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "your-value",
"CAPX_EMAIL": "your-value",
"CAPX_LANE": "your-value",
"X_CLIENT_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add capx-cafe --env CAPX_CHOKEPOINT_URL=your-value --env CAPX_EMAIL=your-value --env CAPX_LANE=your-value --env X_CLIENT_ID=your-value -- npx -y capx-cafeFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "your-value",
"CAPX_EMAIL": "your-value",
"CAPX_LANE": "your-value",
"X_CLIENT_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"capx-cafe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "your-value",
"CAPX_EMAIL": "your-value",
"CAPX_LANE": "your-value",
"X_CLIENT_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- URL of the hosted capx chokepoint that enforces the server-side guardrail on every post
- Whitelisted user email used to authenticate to the chokepoint
CAPX_LANEenvConnection lane: 'byo' (bring your own X app) or 'capx-app' (capx-managed app)X_CLIENT_IDenvX (Twitter) OAuth client ID; required only on the BYO lane
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account vb-tyagi, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Marketing & social mediai
- More stars than 0% of the other 3633 servers in this category
- Published to the registry more recently than 30% of the other 3633 servers in this category
- Basic checks equal to or better than 100% of the other 3633 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is capx café safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: CAPX_CHOKEPOINT_URL, CAPX_EMAIL
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Google Analytics MCP
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
capx café
The safe way to let your AI run your X.
One MCP server. Your X token never touches the agent — and every post clears an enforced guardrail before it ships.
*The guardrail, live — every verdict above is produced by the real chokepoint code (pnpm demo replays it).*
capx café is an agent-native X poster that installs as one MCP server into any coding agent (Claude Code /
Cursor / Codex / Windsurf). A whitelisted user connects their X account once; after that they create /
schedule / post from inside their agent session. The whole product rests on one security thesis: the X
token, the guardrail (casserole), and the send are one inseparable server-side unit — the agent on
your laptop only ever holds a short-TTL session handle, never the token. That's why it structurally can't be
prompt-injected into tweeting a scam. "The AI writes; casserole decides what ships."
Why it's different
Every other "let your AI post" tool has the same flaw: to let an agent post, you paste your X token into a plaintext config right next to an autonomous agent that reads untrusted web pages, issues, and code. One prompt-injection and your account tweets a scam. capx café is the only one that structurally can't be.
- 🔒 Your X token never touches your machine. OAuth completes on capx café's hosted callback; the token lives encrypted in a server-side vault. Your agent holds only a short-TTL, revocable session handle.
- 🛡️ casserole — a *deterministic (non-AI)* six-layer guardrail — runs server-side at the only door to X and checks every post. A blocked post never even decrypts your token (proven by an adversarial test suite).
- 🔗 The token, the guard, and the send are one unit. Skip the plugin and call the server directly — you still hit the guard. The client's checks are cosmetic; the server's are load-bearing.
- ✍️ capx generates nothing. *Your* agent's model writes; capx ships what clears the guard.
→ Full threat model, architecture & the "what we can/can't see" table: [docs/SECURITY.md](docs/SECURITY.md)
How it works
flowchart LR
subgraph M["🖥️ your machine · untrusted"] A["agent model writes the draft"] S["capx skills"] C["capx MCP client holds a session handle · NO token"] end subgraph K["🔒 capx chokepoint · hosted · AGPL-3.0"] AD["admission allowlist · kill-switch"] CAS["casserole 6-layer guardrail"] V["vault the token lives here"] XA["x-adapter the only egress"] end X["🐦 X · /2/tweets"] A --> C S --> C C -->|"short-TTL handle crosses — never the token"| AD AD --> CAS CAS -->|PASS| V --> XA --> X CAS -.->|blocked / held| C
The token, the guardrail, and the send live together behind a trust boundary; your agent can only *ask*.
The guardrail: casserole
Six deterministic layers on every post. Worst result wins — pass / rewrite / hold / block — and a blocked post never even decrypts the token.
flowchart TD
D["draft"] --> AD{"admitted? allowlisted · not killed"} AD -->|no| R["rejected"] AD -->|yes| CAS["casserole L1 eligibility · L2 rate · L3 anti-slop L4 authenticity · L5 kill-switch · L6 audit"] CAS --> VER{"verdict"} VER -->|block| B["blocked — never sent 🔒 token never decrypted"] VER -->|hold| H["held for your review"] VER -->|rewrite| RW["ask the agent to fix"] VER -->|pass| SEND["vault → x-adapter → X ✅"]
60-second quickstart
npx -y capx-cafe # runs the MCP server — add it to your agent's MCP config
Then, inside your agent:
"connect my X account" → opens a browser once; the token stays on the server
"post: shipping the thing today" → clears casserole, or tells you exactly why not "turn my last week of commits into a build-in-public thread" → drafts + queues it
Set CAPX_EMAIL (your whitelisted email) and, for the BYO lane, X_CLIENT_ID (your own X app) in ~/.capx/config.json or your agent's MCP env. A guided setup page hands you the exact callback URL to paste.
Install matrix
| Agent | How |
|---|---|
| Claude Code | /plugin marketplace add vb-tyagi/capx-cafe → /plugin install capx-cafe (MCP + slash commands + skills) |
| Cursor | add to .cursor/mcp.json; skill rules in plugins/capx-cafe/adapters/cursor/ |
| Codex | add to your MCP config; prompt pack in plugins/capx-cafe/adapters/codex/ |
| Windsurf | add to MCP config; workflows in plugins/capx-cafe/adapters/windsurf/ |
| Any MCP agent | point it at npx -y capx-cafe |
| Docker Desktop | docker mcp catalog pull ghcr.io/vb-tyagi/capx-catalog:latest → MCP Toolkit → enable capx café |
What your agent can do
| Tool | What it does |
|---|---|
connect_x | One-time browser OAuth — the token lands in the server vault, never on your machine |
post_now | Post now (clears casserole first). Supports reply-chains and media |
preview | Dry-run a draft through the guardrail without sending — pass / hold / block + why |
audit | The durable record of what capx posted or attempted on your behalf, and its state |
create_loop · list_loops · … | Scheduled posting — a queue you wrote, sent on a schedule, laptop-off |
upload_media | Stream a local image/video to X and attach it (media you made with your own tools) |
whoami | The connected account + its status |
Skills — your work becomes your content
capx lives inside a *coding* agent, so it has what no social scheduler does: your repo, commits, PRs, releases. Skills turn that into posts — automatically, and always through the guardrail.
flowchart LR
G["git commits"] --> BIP["build-in-public drafts a week of posts"] BIP --> Q["loop queue"] Q -->|"1/day · laptop-off"| POST["posted to X"] Q -.->|"runs low"| GAP["gap-alert"] GAP -.->|"top up from new commits"| BIP
The self-refilling content engine: you code → commits accrue → the loop drains as it posts → gap-alert tops it up from the *new* commits. Your normal work *is* the pipeline.
- 🏆 build-in-public · ship-note · changelog-thread · repurpose (blog/README → thread) · launch-thread · til · fix-note
- voice-match (sound like you) · draft-review (lint against the guard) · thread-builder · hook-rewrite
- best-time · cadence-planner · gap-alert · audit-trail · connection-health · quickstart · self-host-guide
- Media directors —
image-director,video-director,prompt-engine,model-guide: capx runs no models; it guides *your* image/video tools (higgsfield, fal, kling, …) and uploads the result. casserole guards your caption; you own the media.
*One canonical SKILL.md per skill, generated for all four agents. capx never writes the content — it makes good content easy and stops bad content regardless of which skill produced it.*
Two lanes
- BYO — bring your own X developer app. You're X's customer and pay X directly — since Feb 2026 that means pre-loading credits (no free X tier for new apps) at ~$0.015/post, $0.20 if the post contains a link. Free on capx café's side; heavy users can self-host the identical image.
- capx-app (creator lane) — post through capx café's shared X app, no developer account needed. Opening as a paid beta (waitlist):
Short $5/Tall $15/Grande $35monthly tiers + top-up packs, quotas enforced server-side at the gate. Full sheet + the math: [docs/ECONOMICS.md](docs/ECONOMICS.md) · policy posture: docs/X-COMPLIANCE.md.
Self-host
The chokepoint is open source (AGPL-3.0). Run the identical image with your own X app, keys, database, and domain — CAPX_DEPLOY_MODE=self-host, zero telemetry to capx. See the self-host-guide skill and docs/HANDOFF.md.
Licensing
MIT for the client and everything it bundles (apps/capx-mcp, core, config, platform-client) plus skills & docs. AGPL-3.0 for the server half (the chokepoint + casserole/captain/counter/canteen/ chef). Full map: [LICENSING.md](LICENSING.md).
Status
Private alpha, whitelist-only. The first real post shipped 2026-07-19 — guardrail-cleared, token never on the machine. Not yet open for public signups.
Dev
Node ≥ 22.6 (TypeScript runs natively via --experimental-strip-types — no build step). pnpm run verify = unit tests across packages / services / apps + tsc. Contributions accepted under the project CLA.
capx café · security · architecture · license