Before you start.

All three paths connect to the same capx café publishing tools. You need Node 22.6 or later, a server URL, an allowed email, and your X app’s OAuth client ID for the developer BYO option. Replace every YOUR_… value below before using the configuration.

Keep existing servers and settings when editing a configuration file. If a capx-cafe entry already exists, update that entry rather than creating another. These examples configure the MCP tools; they do not authorize your X account or publish anything.

Claude Code: install the plugin.

Run these commands inside Claude Code to add the capx café marketplace and install its plugin:

Claude Code plugin commands
/plugin marketplace add vb-tyagi/capx-cafe
/plugin install capx-cafe@capx-cafe

The plugin bundles the MCP server and skills. Installation and service configuration are separate: follow the capx café configuration guide to supply your server URL, allowed email, lane, and X client ID to its MCP server. Ask Claude Code to help apply these values without editing unrelated settings.

If the plugin cannot be found, check that the marketplace was added successfully and inspect Claude Code’s plugin manager for errors. Review the installation source before enabling it.

Cursor: add an MCP server entry.

For a project-level setup, merge the server entry below into .cursor/mcp.json. Cursor also supports a personal global configuration at ~/.cursor/mcp.json. Choose the scope that fits where you want the tools available.

Cursor MCP configuration
{
  "mcpServers": {
    "capx-cafe": {
      "command": "npx",
      "args": [
        "-y",
        "capx-cafe"
      ],
      "env": {
        "CAPX_CHOKEPOINT_URL": "YOUR_SERVER_URL",
        "CAPX_EMAIL": "YOUR_ALLOWED_EMAIL",
        "CAPX_LANE": "byo",
        "X_CLIENT_ID": "YOUR_X_CLIENT_ID"
      }
    }
  }
}

Check Cursor’s MCP settings for the server’s status and available tools. Keep personal configuration values out of shared project commits unless you intend to share them. A valid JSON file still needs the correct values and a working Node installation.

Codex: add a TOML server entry.

Add this block to ~/.codex/config.toml, preserving the rest of the file. Codex defines MCP servers under mcp_servers; the nested env table supplies capx café’s configuration.

Codex MCP configuration
[mcp_servers.capx-cafe]
command = "npx"
args = ["-y", "capx-cafe"]

[mcp_servers.capx-cafe.env]
CAPX_CHOKEPOINT_URL = "YOUR_SERVER_URL"
CAPX_EMAIL = "YOUR_ALLOWED_EMAIL"
CAPX_LANE = "byo"
X_CLIENT_ID = "YOUR_X_CLIENT_ID"

Reload the MCP connection or start a fresh session after saving. Use the official MCP configuration guide for client-specific troubleshooting. The X connection described below is capx café’s browser flow; these stdio settings do not require turning the capx service URL into a remote MCP endpoint.

Check the connection in any agent.

First ask the agent to list capx café’s available tools. Then ask it to connect your X account, follow the URL returned by connect_x, and confirm the handle with whoami.

Try this with your agent

Check whether capx café is configured and list its available tools. Tell me which setup values are missing without printing secrets. If my X account is already connected, show its handle using whoami. Do not publish or create a schedule.

If discovery works but service calls fail, inspect the reported configuration or access error. If no tools appear, check JSON or TOML syntax, Node availability, and the client’s server status. A blocked draft is a separate issue: read its guardrail verdict rather than reinstalling the integration.

Once the connection is healthy, follow the first-post walkthrough. Begin with a preview. Add skill adapters for your client from the repository when you want more guided workflows.

Sources & further reading