Codex is the one tool that connects with a key instead of the browser sign-in, because its browser sign-in for remote servers is not dependable yet. Everything else works the same once it is in place.
Create a key
In your HelpKit dashboard, open Account Settings → MCP and scroll to Connected clients & keys. Create a key there and copy it in one go. Keys start with hk_ and they are long, so avoid retyping any part of it.
Keys stay valid until you delete them, and you can delete one at any time to cut that connection off.
Let Codex set itself up
Paste this into any Codex session, with your own key in place of hk_YOUR_KEY, and it writes its own configuration:
Install the HelpKit MCP server for me. Add this block to ~/.codex/config.toml, then confirm it shows up in "codex mcp list":
[mcp_servers.helpkit]
url = "https://connect.helpkit.so/mcp"
http_headers = { "Authorization" = "Bearer hk_YOUR_KEY" }Then restart Codex so it picks up the new server, and ask it to check your HelpKit setup status.
Or edit the file yourself
Add this block to ~/.codex/config.toml:
[mcp_servers.helpkit]
url = "https://connect.helpkit.so/mcp"
http_headers = { "Authorization" = "Bearer hk_YOUR_KEY" }If it does not work
Almost every failure here is the key: a missing Bearer, a truncated paste, or a key that was deleted.
Powered by