capx café runs on your own machine — the client starts it, so there is no endpoint to ping. 46 installs a week from npm. Last commit 17 Sep 2026.
Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add capx-cafe -e 'CAPX_CHOKEPOINT_URL=<CAPX_CHOKEPOINT_URL>' -e 'CAPX_EMAIL=<CAPX_EMAIL>' -- npx -y capx-cafe{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "<CAPX_CHOKEPOINT_URL>",
"CAPX_EMAIL": "<CAPX_EMAIL>"
}
}
}
}[mcp_servers.capx-cafe]
command = "npx"
args = ["-y", "capx-cafe"]
env = { CAPX_CHOKEPOINT_URL = "<CAPX_CHOKEPOINT_URL>", CAPX_EMAIL = "<CAPX_EMAIL>" }{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "<CAPX_CHOKEPOINT_URL>",
"CAPX_EMAIL": "<CAPX_EMAIL>"
}
}
}
}{
"servers": {
"capx-cafe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"capx-cafe"
],
"env": {
"CAPX_CHOKEPOINT_URL": "<CAPX_CHOKEPOINT_URL>",
"CAPX_EMAIL": "<CAPX_EMAIL>"
}
}
}
}Put your own values in place of
<CAPX_CHOKEPOINT_URL> (URL of the hosted capx chokepoint that enforces the server-side guardrail on every post), <CAPX_EMAIL> (Whitelisted user email used to authenticate to the chokepoint).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CAPX_LANE (Connection lane: 'byo' (bring your own X app) or 'capx-app' (capx-managed app)), X_CLIENT_ID (X (Twitter) OAuth client ID; required only on the BYO lane).
Alternatives to capx café
same job, measured the same wayFastMCP server for posting formatted content to X (Twitter) — Tollbooth-monetized, DPYC-native
X/Twitter read API for agents: search, timelines, Smart Money. Claude/Cursor MCP. Not for posting.
I do everything related to Twitter posting and campaigns
MCP server for the Sorsa.io X/Twitter data API
Run social media with agents. Connect over MCP to plan, write, and post to every network.
One MCP server that gives your AI agent search, AI answer, social, ad and lead data.
Read-only X/Twitter MCP: posts, threads, replies, search via twscrape. No API key.
MCP server for SEO meta tag generation — title, description, Open Graph, Twitter Cards
capx café — questions
Answers built from our own checks of this server.