Skip to main content

One-command setup

From the repo root:
The CLI writes everything Cursor needs:
  • .cursor/mcp.json — MCP server config pointing to npx -y enagrams --mcp
  • .cursor/hooks.json — event-to-script wiring
  • .cursor/hooks/enagrams-hooks.mjs — the hook script itself
Restart Cursor (or re-open the project) so it picks up the new configuration.

Verify

Open the MCP panel in Cursor (command palette → Cursor: Open MCP Settings). You should see enagrams listed as a connected server with 26 tools. In a terminal:
With Cursor open on this project you should see at least one active agent session.

What the Hooks Do

Manual Configuration

If you’d rather set it up by hand, .cursor/mcp.json:
For the hook scripts run npx enagrams init in a scratch directory and copy the generated files — keeping them in sync with the CLI is easier than maintaining them manually.

Troubleshooting

MCP server not appearing in Cursor — fully quit and relaunch Cursor. Restart-Cursor-window is not enough. “Permission denied” on every writemust-tier convention matched. Run convention_list with the file path to see which one. Hooks not firing — check .cursor/hooks.json exists and references .cursor/hooks/enagrams-hooks.mjs. Re-run npx enagrams init to regenerate.