Skip to main content
Codex starts Hoista’s MCP server itself, over stdio. The CLI and the IDE extension share the same settings, so adding it once covers both. You need Hoista on this computer: run hoist doctor to check.

​
Add Hoista

Or add it to ~/.codex/config.toml yourself:
Use the path command -v hoist prints. A full path matters for the IDE extension, which doesn’t always see the same PATH as your terminal.

​
Approve it in Hoista

When Codex starts Hoista, Hoista opens a page in your browser with a code. Check the code matches the one Codex shows, choose What it may do and allow it. If the page doesn’t open, allow it in Agents in the desktop app, or from a terminal:
Start with View only and widen it later in Agent permissions.

​
Add Hoista’s skills

Hoista’s skills teach Codex how to use it well: where to start, how to connect providers and import projects, and how to deploy, fix and manage them.

​
Check it works

Ask Codex: “What projects do I have on Hoista?” It should list your projects. If it doesn’t, see If it doesn’t connect.

​
Hoista on a remote

Codex talks to Hoista on this computer. While a remote is selected (hoist remote use NAME), hoist mcp won’t start. To use the remote, add it to Codex as an HTTP MCP server at its own address: hoist mcp config prints the remote’s /mcp URL. Codex then signs in with OAuth.

​
If it doesn’t connect

  • Run codex mcp list to check Hoista is listed, and hoist doctor to check Hoista itself.
  • To remove it: codex mcp remove hoista, then revoke the agent in Agents or with hoist agents revoke.

Agent permissions

Change or narrow what an agent can do.

Approvals

What Hoista asks you before an agent acts.

Prompts

Prompts to start with.