Skip to main content

​
Configure the connection

Create a Jolts API key. Copy the company-data MCP endpoint from Jolts’ connection guide; the documentation site’s /mcp endpoint searches documentation instead. Merge this into ~/.codex/config.toml, replacing the endpoint placeholder:
In Bash, enter your key privately and launch Codex from that shell:
The environment variable must be available to the process running Codex. A separately launched desktop application does not necessarily inherit this shell’s environment. Never put the key in a prompt or commit it to a configuration file. Jolts uses bearer authentication, not OAuth login.

​
Check the connection

Ask Codex to inspect the available Jolts tools without searching. Expect search_companies, get_companies, and get_usage. Ask it to call get_usage without arguments; this is unmetered. For your first search, follow find active demand and approve the tool call only after reviewing its inputs. Company operations need an active or trialing subscription and consume the same allowance as API requests.

​
If it does not connect

  • Missing environment variable: restart Codex from the shell where you exported it.
  • Unauthorized: check the key is current and belongs to the intended Jolts account.
  • Tools unavailable: inspect your organization’s MCP policy and refresh the connection.
  • Search failed: use the structured error and troubleshooting guide.
See official Codex MCP configuration, the tool reference, and response handling.