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

README.md

@@ -47,6 +47,7 @@ The installer:
 - downloads the latest `cursor-authstack` repository
 - installs each plugin into `~/.cursor/plugins/local/<plugin-name>`
 - verifies each installed plugin root contains `.cursor-plugin/plugin.json`
+- lets Cursor load each plugin's `.mcp.json` through the plugin manifest, including the hosted Scalekit MCP server URL
 - prints the next steps to reload Cursor and confirm the plugins loaded
 
 After it finishes:

plugins/agent-auth/.mcp.json

@@ -1,8 +1,7 @@
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }

plugins/full-stack-auth/.mcp.json

@@ -1,8 +1,7 @@
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }

plugins/mcp-auth/.mcp.json

@@ -1,8 +1,7 @@
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }

plugins/mcp-auth/agents/mcp-auth-troubleshooter.md

@@ -66,7 +66,7 @@ Common failures:
 ### redirect_uri mismatch
 Cause: MCP client cached an old domain and is sending auth requests to a stale URL.
 Fix by client:
-- MCP-Remote: delete `~/.mcp-auth/mcp-remote-<version>` then reconnect.
+- Cursor: open Cursor Settings → MCP, remove the affected MCP server entry, then reconnect.
 - VS Code: open Command Palette → "Authentication: Remove Dynamic Authentication Provider" → reconnect.
 - Claude Desktop: clearing cached auth is NOT currently supported. Workaround: use a different domain/subdomain.
 

plugins/mcp-auth/agents/scalekit-mcp-auth-troubleshooter.md

@@ -45,7 +45,7 @@ If the 401/header/metadata checks fail, classify as “metadata/handshake miscon
 If the handshake looks correct but the client still fails, suspect the client cached an old domain/metadata after a domain change.
 
 Clear cached auth (by client):
-- MCP-Remote: delete `~/.mcp-auth/mcp-remote-<version>` and reconnect.
+- Cursor: open Cursor Settings → MCP, remove the Scalekit MCP server entry, then reconnect.
 - VS Code: run “Authentication: Remove Dynamic Authentication Provider”, remove the cached entry, and reconnect.
 
 If the failing client is Claude Desktop, note that client behavior can differ and some issues are client-specific (see sections below).

plugins/mcp-auth/agents/scalekit-setup.md

@@ -188,14 +188,13 @@ If yes, open or create `.cursor/mcp.json` and merge:
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com/"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }
 ```
 
-Instruct the user to restart Cursor. After restart, an OAuth workflow will launch to authorize the connection.
+Instruct the user to restart Cursor. After restart, Cursor will connect to the hosted Scalekit MCP server and launch an OAuth workflow to authorize the connection.
 
 ## Step 7: Index Scalekit Docs in Cursor (Recommended)
 

plugins/mcp-auth/references/scalekit-mcp-server.md

@@ -441,8 +441,7 @@ The Scalekit MCP server is already hosted and ready to use:
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com/"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }

plugins/modular-scim/.mcp.json

@@ -1,8 +1,7 @@
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }

plugins/modular-sso/.mcp.json

@@ -1,8 +1,7 @@
 {
   "mcpServers": {
     "scalekit": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://mcp.scalekit.com"]
+      "url": "https://mcp.scalekit.com"
     }
   }
 }