Dettivo
Start free trial

§ Troubleshooting

MCP cannot connect

Developer tool

Most often: the dettivo CLI is not in PATH, the agent-host config points at a stale path, or Dettivo.app is not running. Run dettivo install-helper --link, regenerate the host config for your host, and confirm Dettivo is running.

Who this is for

Developers wiring Dettivo into Claude Desktop, Cursor, Codex, or any other MCP host.

Fix path

  1. 01

    Confirm Dettivo.app is running

    The MCP server proxies through the local Dettivo IPC socket. If Dettivo is not running, the socket is gone.

  2. 02

    Confirm the CLI is in PATH

    dettivo install-helper --link symlinks the CLI into ~/.local/bin/. Make sure ~/.local/bin/ is on your shell PATH.

    Terminal

  3. 03

    Regenerate the host config

    Run dettivo mcp config --host claude-desktop --write or dettivo mcp config --host codex --write. For Cursor, run dettivo mcp config --host cursor and paste the emitted JSON into Cursor MCP settings.

    Terminal

  4. 04

    Restart the host

    Claude Desktop, Cursor, or your Codex session must restart to pick up the new MCP server entry.

  5. 05

    Check the host's MCP logs

    Most hosts log MCP stderr. Look for "permission denied", "socket not found", or "token mismatch", each points to a different fix.

§ Related

Just launched

Just launched on your Mac.

One-time license, three active Macs, lifetime updates. $45 once, forever yours.

Buy DettivoDownload