Connect with ChatGPT desktop or Codex
Use the ChatGPT desktop app to ask ForwardFlow questions in plain English. The model runs on BTC Now’s server. Codex CLI and IDE users can use the configuration option below. ChatGPT in a browser has a separate setup.
You need a ForwardFlow access token. Request one from info@btcnow.com; BTC Now will send it privately. No ForwardFlow account is needed.
1. Add the connection
In ChatGPT desktop, open Settings → MCP servers → Add server. Fill in:
| Field | What to enter |
|---|---|
| Name | forwardflow |
| Type | Streamable HTTP |
| URL | https://btcnow-forwardflow.fly.dev/mcp |
| Headers → Key | Authorization |
| Headers → Value | Bearer YOUR_ACCESS_TOKEN |
Replace YOUR_ACCESS_TOKEN with your token, keeping the space after Bearer. Paste it into the header value, not into a chat message.
Leave Bearer token env var and Headers from environment variables empty. Those fields are for a different setup.
Select Save. The connection and token stay saved on this computer; keep its configuration private.
2. Check that it connects
Select Restart when prompted. Open a chat and enter:
/mcp
Check that forwardflow is connected and enabled. Review any permission request to use its tools.
3. Ask your first question
Use ForwardFlow to run the base case. Explain the assumptions and the Holder’s return and cash flows in plain English. Include any warnings from the model.
ChatGPT should use the ForwardFlow tools to calculate the answer. Then try:
Compare that with Bitcoin falling 40% in month six and staying lower. Keep the other assumptions the same. What changes for the Holder?
Need help?
Email info@btcnow.com. Do not include your token in the message or a screenshot.
The connection is missing, fails, or reports that it is busy
- Missing connection: confirm you saved it in the desktop app, restart, then check
/mcpagain. - Invalid token or
401: check theAuthorizationheader, the space afterBearer, and that you replaced the placeholder. Ask BTC Now to confirm your token is active if it still fails. - No tools or an incorrect address: copy the full URL above, including
/mcp, and select Streamable HTTP. - Connected, but no model result: ask ChatGPT explicitly to use the ForwardFlow tools and check their permissions.
- Service busy: wait for the suggested retry interval, then ask again. Invited users share the server’s capacity.
Using ChatGPT in a browser?
This guide is for the desktop app’s custom MCP connection. Saving it does not also connect ChatGPT on the web. See web connection options.
Codex CLI and IDE
Local ChatGPT desktop, Codex CLI and IDE clients share MCP configuration on the same Codex host. A connection saved there does not need to be added again for each client.
If configuring Codex directly, add this entry to your user configuration, normally ~/.codex/config.toml, replacing the placeholder privately:
[mcp_servers.forwardflow]
url = "https://btcnow-forwardflow.fly.dev/mcp"
http_headers = { Authorization = "Bearer YOUR_ACCESS_TOKEN" }
Restart the client. In Codex CLI, use /mcp to check the connection. This service uses the supplied token; codex mcp login is for OAuth servers and is not needed here. Environment-based credentials are also supported, but the variable must exist in the environment of the host running the client.
Setup checked against OpenAI’s MCP documentation on 14 September 2026. Back to AI connections.