Before you start
- Cursor with custom MCP server support
- Permission to edit your project’s MCP configuration
Use a project configuration
Cursor documents remote HTTP MCP servers through a URL entry in .cursor/mcp.json. Merge the example below with your existing configuration; do not replace other servers or add credentials for this public library.
Confirm tool discovery before starting work
Open Cursor’s MCP settings and inspect LazyCoder. Confirm list_recipes and get_recipe are available. This documentation does not establish that your client is connected or that a current LazyCoder outcome has been generated in Cursor.
Use an exact public recipe identity
Return to your selected recipe and copy its starter. Ask the assistant to retrieve the exact ID and version, confirm the release, then ask for the facts it needs. Keep private documents out of catalog tool arguments.
Cursor project configuration
This example uses the server you are viewing. Local clients on this computer can reach localhost; hosted clients require a publicly reachable endpoint. It changes your client only if you run or save it yourself.
Loading this page’s endpoint…
Guidance checked October 28, 2026. Current real-host first-use and generated-output acceptance are pending. Official Cursor MCP documentation ↗
Your next step
Verify discovery in your own client, then use the same selected recipe.