Jesse MCP — connect in Cursor

Make sure Jesse is running and your .env is set up so the MCP server starts and prints a URL (see MCP server setup if you have not done that yet).

Register Jesse in Cursor

Exact labels change as Cursor updates, but the flow is usually:

1. Open Settings and find MCP, Tools & MCP, or similar.
2. Add a server (or equivalent) and paste the address Jesse printed in the terminal. It should end with /mcp and match the host where Jesse runs (often http://localhost:9002/mcp unless you changed MCP_PORT).
3. Save, then restart Cursor if it does not pick up the new server right away.

If something fails, turn on MCP_LOG_IN_TERMINAL in .env while you debug—see Environment variables for MCP.

Agent rules (optional but recommended)

Jesse automatically writes and maintains AGENTS.md at the project root every time you run jesse run, so Cursor can read the rules without you pasting anything. See MCP agent rules for details on what's in the file, how the auto-sync works, and how to add your own notes without losing them on upgrade.

• MCP in Cursor
• MCP integrations (help)

Same machine, same network story

If Cursor runs on Windows and Jesse runs inside WSL (or the other way around), localhost can refer to different machines. If you see connection errors, check Cursor’s docs for WSL or remote MCP setup, or run Jesse and Cursor in the same environment so they share one loopback network.