Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a new documentation guide for setting up Model Context Protocol (MCP) to interact with local Postgres and Trino instances. The feedback highlights a potential inaccuracy regarding the configuration file path, noting that Cursor typically manages MCP servers through its settings UI rather than a ~/.cursor/mcp.json file.
| @@ -0,0 +1,44 @@ | |||
| # Cursor MCP: Postgres and Trino (local) | |||
|
|
|||
| Quick setup so the Cursor agent can run SQL against **local** Postgres (default **15432**) and Trino (**8080**) from docker-compose. Config lives in **`~/.cursor/mcp.json`** (or **Cursor Settings → MCP**). Restart Cursor after changes. | |||
There was a problem hiding this comment.
Cursor does not natively use ~/.cursor/mcp.json for its MCP configuration. Native MCP servers in Cursor are typically configured through the UI at Cursor Settings > Features > MCP. While the provided JSON format is standard for the Claude Desktop app, for Cursor you will need to manually add each server in the settings pane using the command and args specified in the example. If you intended to provide instructions for the Claude Desktop app, the standard path on macOS is ~/Library/Application Support/Claude/claude_desktop_config.json.
No description provided.