Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.
Connect Runs on your machine
claude mcp add capx-cafe -e CAPX_CHOKEPOINT_URL=<CAPX_CHOKEPOINT_URL> -e CAPX_EMAIL=<CAPX_EMAIL> -e CAPX_LANE=<CAPX_LANE> -e X_CLIENT_ID=<X_CLIENT_ID> -- npx -y [email protected]{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CAPX_CHOKEPOINT_URL": "<CAPX_CHOKEPOINT_URL>",
"CAPX_EMAIL": "<CAPX_EMAIL>",
"CAPX_LANE": "<CAPX_LANE>",
"X_CLIENT_ID": "<X_CLIENT_ID>"
}
}
}
}{
"mcpServers": {
"capx-cafe": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CAPX_CHOKEPOINT_URL": "<CAPX_CHOKEPOINT_URL>",
"CAPX_EMAIL": "<CAPX_EMAIL>",
"CAPX_LANE": "<CAPX_LANE>",
"X_CLIENT_ID": "<X_CLIENT_ID>"
}
}
}
}{
"servers": {
"capx-cafe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CAPX_CHOKEPOINT_URL": "<CAPX_CHOKEPOINT_URL>",
"CAPX_EMAIL": "<CAPX_EMAIL>",
"CAPX_LANE": "<CAPX_LANE>",
"X_CLIENT_ID": "<X_CLIENT_ID>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
CAPX_CHOKEPOINT_URLRequired | URL of the hosted capx chokepoint that enforces the server-side guardrail on every post |
CAPX_EMAILRequired | Whitelisted user email used to authenticate to the chokepoint |
CAPX_LANEOptional | Connection lane: 'byo' (bring your own X app) or 'capx-app' (capx-managed app) |
X_CLIENT_IDOptional | X (Twitter) OAuth client ID; required only on the BYO lane |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 3 Sep 2026 |
| Last updated | 3 Sep 2026 |
| Registry name | io.github.vb-tyagi/capx-cafe |
More marketing and seo servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.