Skip to content

Replace mcp-remote config with direct url for remote MCP server#7399

Merged
ankur-arch merged 1 commit intomainfrom
ptl-690-mcp-server-incompatible-with-mcp-remote0132-due-to-incorrect
Dec 17, 2025
Merged

Replace mcp-remote config with direct url for remote MCP server#7399
ankur-arch merged 1 commit intomainfrom
ptl-690-mcp-server-incompatible-with-mcp-remote0132-due-to-incorrect

Conversation

@kristof-siket
Copy link
Contributor

@kristof-siket kristof-siket commented Dec 17, 2025

Summary

Modern IDEs (Cursor, VS Code, etc.) now support direct remote MCP connections without mcp-remote. This PR updates the documentation to use the simpler URL-based configuration.

Changes

Replaced the mcp-remote command-based configuration:

"Prisma-Remote": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://mcp.prisma.io/mcp"]
}

With the simpler direct URL config:

"Prisma-Remote": {
  "url": "https://mcp.prisma.io/mcp"
}

Files Changed

  • content/250-postgres/350-integrations/400-mcp-server.mdx
  • content/250-postgres/350-integrations/500-vscode.mdx
  • content/900-ai/index.mdx

Related

Fixes: PTL-690

Summary by CodeRabbit

  • Documentation
    • Updated Prisma MCP server configuration examples across documentation to use simplified URL-based format, replacing the previous command-line invocation approach for easier configuration.

✏️ Tip: You can customize this high-level summary in your review settings.

Modern IDEs now support direct remote MCP connections without mcp-remote.
This change updates the documentation to use the simpler url-based config.

Fixes: PTL-690
@github-actions
Copy link
Contributor

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 17, 2025

Walkthrough

Three documentation files were updated to replace MCP remote server configuration from command-based invocation (command: "npx" with args array) to a direct URL field format across multiple configuration snippet examples in Postgres, VS Code integration, and AI documentation sections.

Changes

Cohort / File(s) Summary
MCP remote server configuration documentation
content/250-postgres/350-integrations/400-mcp-server.mdx, content/250-postgres/350-integrations/500-vscode.mdx, content/900-ai/index.mdx
Updated Prisma-Remote MCP server configuration examples from command: "npx", args: ["-y", "mcp-remote", "URL"] to url: "URL" across multiple configuration snippets (Remote MCP server usage, VS Code integration, Cursor settings, Claude Desktop, Windsurf configs)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Changes are purely documentation/example updates with homogeneous repetition of the same configuration replacement pattern
  • No logic, error handling, or code structure modifications
  • Straightforward find-and-replace style edits across three files with identical transformations

Possibly related PRs

Pre-merge checks

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the primary change: replacing mcp-remote command-based configuration with direct URL configuration across documentation files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96f5587 and e18f502.

📒 Files selected for processing (3)
  • content/250-postgres/350-integrations/400-mcp-server.mdx (6 hunks)
  • content/250-postgres/350-integrations/500-vscode.mdx (1 hunks)
  • content/900-ai/index.mdx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Check internal links
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (10)
content/250-postgres/350-integrations/500-vscode.mdx (1)

94-96: LGTM! Configuration correctly updated to use direct URL.

The change from command-based (npx with mcp-remote) to direct URL configuration aligns with the PR objectives and simplifies the setup for modern IDEs.

content/900-ai/index.mdx (1)

71-73: LGTM! JSON configuration correctly simplified.

The URL-based configuration is cleaner and aligns with modern IDE support. The CLI example on line 80 appropriately remains unchanged since it demonstrates a different use case (manual server startup).

content/250-postgres/350-integrations/400-mcp-server.mdx (8)

51-53: LGTM! Primary usage example correctly updated.

This establishes the correct pattern for remote MCP server configuration using the direct URL approach.


155-157: LGTM! VS Code configuration consistent across documentation.

This matches the configuration shown in the VS Code integration page (500-vscode.mdx).


210-212: LGTM! Cursor global configuration correctly updated.

The change appropriately uses the direct URL approach for the global configuration file.


229-231: LGTM! Cursor project configuration correctly updated.

Consistent with the global configuration example and uses the simplified URL-based approach.


277-279: LGTM! Windsurf global configuration correctly updated.

The URL-based configuration is properly applied here, though note the inconsistency flagged in the Settings UI example above.


341-343: LGTM! Claude Desktop configuration correctly updated.

The URL-based approach is appropriately applied for Claude Desktop integration.


366-390: No action required. The OpenAI Agents SDK MCPServerStdio example is correctly using the command-based approach. MCPServerStdio is designed for local subprocess-based servers only; for direct URL-based remote connections, the SDK provides MCPServerStreamableHttp and MCPServerSse classes instead. The example's pattern is the appropriate way to invoke a remote server wrapper via command line.


319-321: Verify Claude Code CLI MCP add command capabilities before suggesting changes.

The current example uses a command-based approach. Without confirmed documentation that Claude Code CLI supports or should support direct URL configuration, this syntax may be correct and intentional. Recommend providing evidence (e.g., official CLI documentation or changelog) if suggesting an alternative syntax.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Contributor

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

  • This PR does not change any pages in a way that would require a redirect.

@cloudflare-workers-and-pages
Copy link

Deploying docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: e18f502
Status: ✅  Deploy successful!
Preview URL: https://b8a3c102.docs-51g.pages.dev
Branch Preview URL: https://ptl-690-mcp-server-incompati.docs-51g.pages.dev

View logs

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
content/250-postgres/350-integrations/400-mcp-server.mdx (2)

184-197: Critical: Inconsistent configuration in Cursor Settings UI example.

Lines 192-194 still use the old command-based configuration (command: "npx" with args: ["-y", "mcp-remote", ...]), but the PR updates other Cursor examples to use the direct URL approach (see lines 210-212). Since the PR objectives state that "Modern IDEs (Cursor, VS Code, etc.) now support direct remote MCP connections without using mcp-remote", this Settings UI example should also use the URL-based configuration for consistency.

Apply this diff to update the Cursor Settings UI example:

     {
       "mcpServers": {
         "Prisma-Local": {
           "command": "npx",
           "args": ["-y", "prisma", "mcp"]
         },
         "Prisma-Remote": {
-          "command": "npx",
-          "args": ["-y", "mcp-remote", "https://mcp.prisma.io/mcp"]
+          "url": "https://mcp.prisma.io/mcp"
         }
       }
     }

250-264: Critical: Inconsistent configuration in Windsurf Settings UI example.

Lines 259-261 still use the old command-based configuration, but the Windsurf global configuration example (lines 277-279) correctly uses the URL-based approach. This inconsistency will confuse users and contradicts the PR's objective to use direct URL configuration for modern IDEs.

Apply this diff to update the Windsurf Settings UI example:

     {
       "mcpServers": {
         "Prisma-Local": {
           "command": "npx",
           "args": ["-y", "prisma", "mcp"]
         },
         "Prisma-Remote": {
-          "command": "npx",
-          "args": ["-y", "mcp-remote", "https://mcp.prisma.io/mcp"]
+          "url": "https://mcp.prisma.io/mcp"
         }
       }
     }
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96f5587 and e18f502.

📒 Files selected for processing (3)
  • content/250-postgres/350-integrations/400-mcp-server.mdx (6 hunks)
  • content/250-postgres/350-integrations/500-vscode.mdx (1 hunks)
  • content/900-ai/index.mdx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Check internal links
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (10)
content/250-postgres/350-integrations/500-vscode.mdx (1)

94-96: LGTM! Configuration correctly updated to use direct URL.

The change from command-based (npx with mcp-remote) to direct URL configuration aligns with the PR objectives and simplifies the setup for modern IDEs.

content/900-ai/index.mdx (1)

71-73: LGTM! JSON configuration correctly simplified.

The URL-based configuration is cleaner and aligns with modern IDE support. The CLI example on line 80 appropriately remains unchanged since it demonstrates a different use case (manual server startup).

content/250-postgres/350-integrations/400-mcp-server.mdx (8)

51-53: LGTM! Primary usage example correctly updated.

This establishes the correct pattern for remote MCP server configuration using the direct URL approach.


155-157: LGTM! VS Code configuration consistent across documentation.

This matches the configuration shown in the VS Code integration page (500-vscode.mdx).


210-212: LGTM! Cursor global configuration correctly updated.

The change appropriately uses the direct URL approach for the global configuration file.


229-231: LGTM! Cursor project configuration correctly updated.

Consistent with the global configuration example and uses the simplified URL-based approach.


277-279: LGTM! Windsurf global configuration correctly updated.

The URL-based configuration is properly applied here, though note the inconsistency flagged in the Settings UI example above.


341-343: LGTM! Claude Desktop configuration correctly updated.

The URL-based approach is appropriately applied for Claude Desktop integration.


366-390: No action required. The OpenAI Agents SDK MCPServerStdio example is correctly using the command-based approach. MCPServerStdio is designed for local subprocess-based servers only; for direct URL-based remote connections, the SDK provides MCPServerStreamableHttp and MCPServerSse classes instead. The example's pattern is the appropriate way to invoke a remote server wrapper via command line.


319-321: Verify Claude Code CLI MCP add command capabilities before suggesting changes.

The current example uses a command-based approach. Without confirmed documentation that Claude Code CLI supports or should support direct URL configuration, this syntax may be correct and intentional. Recommend providing evidence (e.g., official CLI documentation or changelog) if suggesting an alternative syntax.

@ankur-arch ankur-arch merged commit a4bbbe7 into main Dec 17, 2025
8 checks passed
@ankur-arch ankur-arch deleted the ptl-690-mcp-server-incompatible-with-mcp-remote0132-due-to-incorrect branch December 17, 2025 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments