Optional Hedy CLI

Use Hedy locally when your AI client can run a shell.

The full remote Hedy MCP endpoint at https://mcp.hedyassist.com/mcp remains the default and needs no local installation. Install the Hedy CLI only for shell-capable Cursor or Claude Code workflows that use the intentionally minimal /mcp/cli guidance surface.

Use the full Hedy MCP Get a connector token
Verified downloads

Hedy CLI releases

The page reads the public release metadata at runtime. It shows a Windows or Linux download only after the platform, architecture, package kind, HTTPS path, SHA-256, and signature status pass validation.

Checking the latest Hedy CLI release…

After installation

  1. Connect a shell-capable client to https://mcp.hedyassist.com/mcp/cli with the same Hedy account you already use.
  2. Ask that client to run a local hedy command. If the CLI is not authenticated, it returns a setupRequestId instead of asking you to paste a token.
  3. The CLI MCP already knows the next step: issue a short-lived enrollment code, then run hedy login --complete-setup <enrollmentCode> --persist. The CLI writes HEDY_TOKEN into the selected shell profile and never prints the bearer.
  4. The selected profile contains a long-lived connector token. Remove the marked Hedy block from that file if you want to revoke local access, then revoke the connector in Admin.
  5. Manual hedy login --token still works. Do not place a bearer in a repository, prompt, log, or generated file.
  6. Use the full MCP URL instead when the client needs Hedy's complete tool, resource, and prompt surface.

Related connector setup

Get an authenticated connector configuration from the Hedy Workspace Connect AI page. The Hedy CLI is separate from the QuickBooks Desktop connector, which is a Windows-only local accounting integration.