descriptions to use local version of mcp-remote for claude desktop

Author: halllo

MyMCPServer.Sse/VibeTool.cs

@@ -37,18 +37,18 @@ public IEnumerable<ContentBlock> GetVibe(string location)
 			return
 			[
 				new TextContentBlock { Text = $"Curious vibes for {name} in {location}." },
-				new EmbeddedResourceBlock
-				{
-					Resource = new BlobResourceContents
-					{
-						MimeType = "image/jpeg",
-						Uri = "https://images.pexels.com/photos/3779448/pexels-photo-3779448.jpeg",
-					},
-					Meta = new JsonObject
-					{
-						["altText"] = $"A man listening.",
-					},
-				},
+				// new EmbeddedResourceBlock //seems to break Claude Desktop
+				// {
+				// 	Resource = new BlobResourceContents
+				// 	{
+				// 		MimeType = "image/jpeg",
+				// 		Uri = "https://images.pexels.com/photos/3779448/pexels-photo-3779448.jpeg",
+				// 	},
+				// 	Meta = new JsonObject
+				// 	{
+				// 		["altText"] = $"A man listening.",
+				// 	},
+				// },
 			];
 		}
 	}

MyMCPServer.Sse/claude_desktop.cmd

@@ -1,2 +1,2 @@
-set NODE_OPTIONS=--use-system-ca
+set NODE_TLS_REJECT_UNAUTHORIZED=0
 npx mcp-remote http://localhost:5253/bot 63113 --static-oauth-client-info "{\"client_id\":\"mcp-remote\"}"

MyMCPServer.Sse/claude_desktop_fnm.cmd

@@ -1,4 +1,4 @@
 cd C:\Users\Manuel.Naujoks\AppData\Roaming\fnm\node-versions\v22.14.0\installation
 $Env:NODE_TLS_REJECT_UNAUTHORIZED=0
 set NODE_TLS_REJECT_UNAUTHORIZED=0
-npx mcp-remote@0.1.18 http://localhost:5253 --transport http-only
+npx mcp-remote 'http://localhost:5253/bot' 63113 --static-oauth-client-info '{\"client_id\":\"mcp-remote\"}'

MyMCPServer.Sse/mcp-remote-oauth-client-info.json

@@ -0,0 +1,3 @@
+{
+  "client_id": "mcp-remote"
+}

README.md

@@ -105,6 +105,16 @@ set NODE_OPTIONS=--use-system-ca
 npx mcp-remote http://localhost:5253/bot 63113 --static-oauth-client-info "{\"client_id\":\"mcp-remote\"}"
 ```
 
+If `set NODE_OPTIONS=--use-system-ca` does not work anymore (`--use-system-ca is not allowed in NODE_OPTIONS`), consider `$env:NODE_TLS_REJECT_UNAUTHORIZED = "0"`.
+
+Powershell does have an escaping problem, so we best put the oauth data in a separate json file and reference it like this:
+
+```powershell
+npx mcp-remote 'http://localhost:5253/bot' 63113 --static-oauth-client-info "@D:\McpExperiments\MyMCPServer.Sse\mcp-remote-oauth-client-info.json"
+```
+
+In the `claude_desktop_config.json` it looks like this:
+
 ```json
 {
     "mcpServers": {
@@ -115,13 +125,14 @@ npx mcp-remote http://localhost:5253/bot 63113 --static-oauth-client-info "{\"cl
                 "http://localhost:5253/bot",
                 "63113",
                 "--static-oauth-client-info",
-                "{\"client_id\":\"mcp-remote\"}"
+                "@D:\\McpExperiments\\MyMCPServer.Sse\\mcp-remote-oauth-client-info.json"
             ],
             "env": {
                 "NODE_OPTIONS": "--use-system-ca"
             }
         }
-    }
+    },
+    "isUsingBuiltInNodeForMcp": false
 }
 ```
 
@@ -171,6 +182,21 @@ try {
 }
 ```
 
+I have proposed the fix with [Resource metadata is remembered throughout the entire login flow. #167](https://github.com/geelen/mcp-remote/pull/167). Until this is merged, we can to compile `mcp-remote` locally and set it up like this:
+
+```bash
+git clone https://github.com/halllo/mcp-remote.git
+cd mcp-remote
+git checkout -b remembers_resource_metadata origin/remembers_resource_metadata
+pnpm install
+pnpm build
+npm link #make it available everywhere
+npm list -g --depth=0 #to verify its actually available
+npx mcp-remote #use linked version everywhere
+```
+
+Make sure your Claude Desktop instance does not use its built-in Node.js, but instead uses your operating system's version of Node.js. Under Settings / Extensions / Advanced Settings you should see the same Node.js version that you used when you ran `npm link`.
+
 ## ChatGPT
 
 MCP support requires ChatGPT Plus. Then users can enable "Developer mode" (which is still in BETA) and create a new connector. Custom OAuth `client_id` is not supported.