capx café
Bring the basics.
The available developer option uses your own X developer app. You will need a compatible coding agent, Node 22.6 or later, your X app’s OAuth client ID, a capx café server URL, and an email allowed on that server.
If you do not have hosted access, ask about it before expecting publishing calls to work. Self-hosting is also available. The developer option has no capx subscription; your agent, X usage, and any self-hosting infrastructure are separate costs. The pricing page explains those boundaries.
Add the tools to your agent.
Open the setup section and choose your client. Claude Code has a plugin installation path; other clients can launch the capx-cafe package as a stdio MCP server. The agent setup guide includes copyable examples.
Configure CAPX_CHOKEPOINT_URL, CAPX_EMAIL, CAPX_LANE=byo, and X_CLIENT_ID. Use your actual allowed email and app client ID. The client ID identifies the app; do not substitute an X password, client secret, or access token.
Reload the agent’s MCP connection if necessary. Ask it to list the capx café tools it can see. Tool discovery confirms installation, but does not confirm your account is connected: capx café can expose its tool list before account configuration is complete.
Connect your X account.
Ask your agent to connect your X account. It calls connect_x and returns an authorization URL. Complete authorization in the browser, checking the account and requested access.
The callback goes to the capx café service, where the X token is stored in the vault. Your agent receives a short-lived session handle. Ask it to call whoami and show the connected handle and status before proceeding.
Draft something real, then preview it.
Choose one change that has shipped and is appropriate to share. Keep the first attempt to a standalone text post so the wording and the publishing steps are easy to inspect.
Try this with your agent
Read the latest commit I have marked as ready to share. Draft one specific X post about the change and why it matters. Do not include private details or unsupported claims. Run the draft through capx café preview and show me the text and verdict. Do not publish or schedule it.
The agent writes the words. The preview tool checks the proposed post without sending it to X. If the verdict calls for a rewrite, hold, or block, inspect the stated reason. Correct the underlying issue rather than repeating the same request or bypassing the guardrail.
Publish the approved version.
Read the final text and confirm that its claims match the source. When you are ready, explicitly ask the agent to publish that exact draft. post_now is the step that sends a real post; the guardrail runs at the publishing boundary again.
Inspect the returned result and check the post on X. If a request times out or its outcome is unclear, ask the agent to inspect the audit history before retrying. Avoid turning uncertainty into a duplicate post.
If something stops you.
- No tools: check the agent configuration and whether Node and npx are available to the agent process.
- Access rejected: check the server URL and allowed email.
- Connection needs authorization: reconnect through the browser and check
whoami. - Draft rejected: read the verdict. It may concern content, account eligibility, or limits rather than installation.