Codex MCP setup: add vbtnl as a remote MCP server

Codex connects to vbtnl as a remote MCP server. You need a vbtnl account and the Codex CLI.

Option 1: sign in (recommended)

codex mcp add vbtnl --url https://api.vbtnl.com/mcp
codex mcp login vbtnl

The second command opens a vbtnl page in your browser: log in and press Allow.

Option 2: personal token

Create a personal token in your vbtnl account (the value is shown once) and put it in an environment variable:

export VBTNL_TOKEN="YOUR_TOKEN"
codex mcp add vbtnl --url https://api.vbtnl.com/mcp --bearer-token-env-var VBTNL_TOKEN

Add the export line to your shell profile so the variable is set in every new terminal.

Check the connection

codex mcp list

vbtnl should be in the list. Open a new Codex session and ask:

List my vbtnl projects.

Deploy your first app

Build a FastAPI service with a /health check and host it on vbtnl.

Codex writes the files into the project on vbtnl, runs it and gives you a draft address. Say "ship it" to publish to production.

Troubleshooting

• Codex does not see the tools. Servers are loaded when a session starts: open a new session after codex mcp add.
• Authorization errors with a token. Check that VBTNL_TOKEN is set in the terminal where you start Codex: echo $VBTNL_TOKEN.
• Remove the server: codex mcp remove vbtnl.