Skip to content

chore: use native Cursor MCP config instead of mcp-remote#9

Closed
saif-at-scalekit wants to merge 2 commits into
mainfrom
preview/native-mcp-config
Closed

chore: use native Cursor MCP config instead of mcp-remote#9
saif-at-scalekit wants to merge 2 commits into
mainfrom
preview/native-mcp-config

Conversation

@saif-at-scalekit
Copy link
Copy Markdown
Collaborator

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

  • mcp-auth
  • modular-sso
  • modular-scim
  • full-stack-auth
  • agent-auth

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.
@saif-at-scalekit
Copy link
Copy Markdown
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.

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