Capx café MCP Server

Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.

Local serverstdio

What is the Capx café MCP Server?

Capx café is an MCP integration. Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.

Packages and local setup

The published npm package is capx-cafe, version 0.1.3. Its declared MCP transport is stdio.

The package declares CAPX_CHOKEPOINT_URL (required): URL of the hosted capx chokepoint that enforces the server-side guardrail on every post; CAPX_EMAIL (required): Whitelisted user email used to authenticate to the chokepoint; 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.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related social media & marketing MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
CAPX_CHOKEPOINT_URLURL of the hosted capx chokepoint that enforces the server-side guardrail on every postYes
CAPX_EMAILWhitelisted user email used to authenticate to the chokepointYes
CAPX_LANEConnection lane: 'byo' (bring your own X app) or 'capx-app' (capx-managed app)Optional
X_CLIENT_IDX (Twitter) OAuth client ID; required only on the BYO laneOptional