chore: use native Cursor MCP config instead of mcp-remote#9
Closed
saif-at-scalekit wants to merge 2 commits into
Closed
chore: use native Cursor MCP config instead of mcp-remote#9saif-at-scalekit wants to merge 2 commits into
saif-at-scalekit wants to merge 2 commits into
Conversation
saif-at-scalekit
pushed a commit
that referenced
this pull request
May 12, 2026
Cursor now supports native MCP server URLs directly. Removes the npx mcp-remote proxy from both plugin .mcp.json files, updates the hosted-server code example in scalekit-mcp-server.md, and replaces MCP-Remote troubleshooting steps with Cursor-native instructions in the MCP auth troubleshooter agent. Folds in the changes from PR #9.
Collaborator
Author
|
Folded into #12 — the consolidation PR now uses the native URL format for .mcp.json and includes the updated troubleshooter agent docs. Closing this as superseded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
All 5 plugin `.mcp.json` files updated to use Cursor's native direct-URL MCP config instead of the mcp-remote proxy.
Before:
```json
{ "mcpServers": { "scalekit": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.scalekit.com"] } } }
```
After:
```json
{ "mcpServers": { "scalekit": { "url": "https://mcp.scalekit.com" } } }
```
Cursor supports native HTTP MCP connections. mcp-remote is preserved as a fallback in the developer docs for clients that fail the OAuth flow.
Plugins updated