Monk MCP is not enabled by default.If Monk is installed directly in Cursor, you do everything in Cursor itself.Make sure:
Monk is installed in Cursor
the project is open in Cursor
In Cursor, run:
Copy
Monk: Manage MCP Server
Then make sure:
you ran Monk: Manage MCP Server
you chose Enable MCP server
For Cursor, it is best to include Cursor in the generated target list. If you want the default experience, choose Smart defaults when Monk asks which clients it should configure.Cursor discovers MCP servers from project configuration in .cursor/mcp.json and merges that with any global MCP config.Monk writes the project-local file for you in the same workspace.Read more: Install Monk, MCP Getting Started
Cursor’s MCP docs recommend saving the config and restarting Cursor so the server is loaded cleanly.If Monk was already enabled while Cursor was open, fully quit and reopen Cursor after the Monk config has been generated.Read more: Cursor MCP integrations
Cursor Agent picks up MCP tools automatically and uses them when relevant.By default, Cursor asks for approval before using MCP tools. This is the safest option and a good default for Monk.If you want fewer prompts, you can change that behavior in Cursor’s MCP settings, but most teams should leave approvals enabled at first.You can also toggle tools on or off from the tools list if you want tighter control.