Skip to main content
bex.co
419

MCP config generator

Pick your agent client and how it should sign in. You get the exact command or config file that connects it to the Bex MCP server, where it goes, and how to check the connection.

Formats come from each client's own documentation, with the date they were checked. Tokens are never written into a file: configs reference `BEX_TOKEN` or let the client ask for it.

These tools run entirely in your browser. Nothing you paste or drop is uploaded, stored, or sent to analytics.

Agent client
Sign-in
Bex installation
Access to grant

Run this for Claude Code

claude mcp add --transport http bex-api https://api.bex.co/mcp

Connect and check

  1. Run the command in a terminal.
  2. Sign in: run /mcp in the client and complete the browser sign-in and consent.
  3. Consent to bex.read only to start: the agent can inspect but not change anything.
  4. Check the connection with a read-only first prompt: “List my Bex workspaces. In the workspace I choose, list services and report their IDs and deployment state. Do not change any resources yet.”

Claude Code format checked against its documentation on 2026-09-26. Source