MPC server connection problem with Claude desktop

Configuration
1

Thanks to the great work of @bertrandda (thanks) for the integration of MCP into Gladys and for his Agent IA- MCP tutorial in the community I tried to install the MCP integration on my Gladys instance. I am a Gladys Plus subscriber and I am trying to test with Claude Desktop

I created the MCP Server API Key in the MCP integration of Gladys

Checking the installation path of mcp-proxy on my W11 PC

PS C:\Users\franc> where.exe mcp-proxy

C:\Users\franc\.local\bin\mcp-proxy.exe

PS C:\Users\franc>

fichier de configuration dans Claude Desktop

Capture d’écran_flotée (1)
Capture d’écran_flotée (1)1479×714 58.6 KB

Problem: Connection error between the MCP Gladys server

2

Hi @Francis66
I haven’t run any tests yet but at first glance in your config file, on the command line you have \\\\ and \\, I’d say either you need doubles or singles but not a mix.

3

Thanks @mutmut for your reply. Indeed there was a lapse of attention on my part because I copied the JSON as-is into the config file after checking it with https://jsonformatter.curiousconcept.com/. This was due to an escape character error \. I have just corrected it to
« command »: « C:\\Users\\franc\\.local\\bin\\mcp-proxy.exe », and I still don’t have a connection between Claude and the MCP server on Gladys

1 Like
4

Strange: when composing my message I put 2 backslashes \ and I only see one.

5

@Francis66 Do you have the error message with more details?

6

The Discourse editor removes the first backslash, that’s why I wrote it as \\\\ :wink:

7

Thanks to Mutmut.

Here are the log files. I masked the authorization keys.

MCP file

2025-11-11T07:05:37.813Z \[info\] \[gladys\] Initializing server…
2025-11-11T07:05:37.934Z \[info\] \[gladys\] Using MCP server command: C:\\Users\franc.local\bin\\mcp-proxy.exe with args and path: {
args: \[
‹ http://192.168.1.29/api/v1/service/mcp/proxy ›,
‹ –transport ›,
‹ streamablehttp ›,
‹ –header ›,
‹ Authorization: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ›,
\[length\]: 5
\],
paths: \[
‹ C:\\Program Files\\nodejs ›,
‹ C:\\windows\\system32 ›,
‹ C:\\windows ›,
‹ C:\\windows\\System32\\Wbem ›,
‹ C:\\windows\\System32\\WindowsPowerShell\\v1.0\\ ›,
‹ C:\\windows\\System32\\OpenSSH\\ ›,
‹ C:\\Program Files\\HP\\HP One Agent ›,
‹ C:\\Program Files\\dotnet\\ ›,
‹ C:\\Program Files\\Git\\cmd ›,
‹ C:\\Program Files\\nodejs\\ ›,
‹ C:\\Users\\franc\\.local\\bin ›,
‹ C:\\Users\\franc\\AppData\\Local\\Microsoft\\WindowsApps ›,
‹ C:\\Users\\franc\\AppData\\Local\\Programs\\Microsoft VS Code\\bin ›,
‹ C:\\Users\\franc\\AppData\\Roaming\\npm ›,
\[length\]: 14
\]
}
2025-11-11T07:05:37.996Z \[info\] \[gladys\] Server started and connected successfully
2025-11-11T07:05:38.190Z \[error\] \[gladys\] spawn C:\\Users\franc.local\bin\\mcp-proxy.exe ENOENT
2025-11-11T07:05:38.193Z \[info\] \[gladys\] Server transport closed
2025-11-11T07:05:38.194Z \[info\] \[gladys\] Client transport closed
2025-11-11T07:05:38.196Z \[info\] \[gladys\] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
2025-11-11T07:05:38.196Z \[error\] \[gladys\] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging)
2025-11-11T07:05:38.198Z \[info\] \[gladys\] Client transport closed

MCP-server-gladys file

2025-11-11T07:05:37.813Z \[gladys\] \[info\] Initializing server… { metadata: undefined }
2025-11-11T07:05:37.933Z \[gladys\] \[info\] Using MCP server command: C:\\Users\franc.local\bin\\mcp-proxy.exe with args and path: {
metadata: {
args: \[
‹ http://192.168.1.29/api/v1/service/mcp/proxy ›,
‹ –transport ›,
‹ streamablehttp ›,
‹ –header ›,
‹ Authorization: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ›,
\[length\]: 5
\],
paths: \[
‹ C:\\Program Files\\nodejs ›,
‹ C:\\windows\\system32 ›,
‹ C:\\windows ›,
‹ C:\\windows\\System32\\Wbem ›,
‹ C:\\windows\\System32\\WindowsPowerShell\\v1.0\\ ›,
‹ C:\\windows\\System32\\OpenSSH\\ ›,
‹ C:\\Program Files\\HP\\HP One Agent ›,
‹ C:\\Program Files\\dotnet\\ ›,
‹ C:\\Program Files\\Git\\cmd ›,
‹ C:\\Program Files\\nodejs\\ ›,
‹ C:\\Users\\franc\\.local\\bin ›,
‹ C:\\Users\\franc\\AppData\\Local\\Microsoft\\WindowsApps ›,
‹ C:\\Users\\franc\\AppData\\Local\\Programs\\Microsoft VS Code\\bin ›,
‹ C:\\Users\\franc\\AppData\\Roaming\\npm ›,
\[length\]: 14
\]
}
} %o
2025-11-11T07:05:37.996Z \[gladys\] \[info\] Server started and connected successfully { metadata: undefined }
‹ C:\\Users › n’est pas reconnu en tant que commande interne
ou externe, un programme ex cutable ou un fichier de commandes.
2025-11-11T07:05:38.190Z \[gladys\] \[error\] spawn C:\\Users\franc.local\bin\\mcp-proxy.exe ENOENT {
metadata: {
context: ‹ connection ›,
stack: ‹ Error: spawn C:\\Users\\franc\\.local\\bin\\mcp-proxy.exe ENOENT\\n › +
’    at e (C:\\Users\\franc\\AppData\\Local\\AnthropicClaude\\app-1.0.332\\resources\\app.asar\\.vite\\build\\index.js:192:7338)\\n’ +
’    at n (C:\\Users\\franc\\AppData\\Local\\AnthropicClaude\\app-1.0.332\\resources\\app.asar\\.vite\\build\\index.js:192:7665)\\n’ +
’    at a.emit (C:\\Users\\franc\\AppData\\Local\\AnthropicClaude\\app-1.0.332\\resources\\app.asar\\.vite\\build\\index.js:192:7556)\\n’ +
’    at ChildProcess._handle.onexit (node:internal/child_process:293:12)’
}
}
2025-11-11T07:05:38.193Z \[gladys\] \[info\] Server transport closed { metadata: undefined }
2025-11-11T07:05:38.194Z \[gladys\] \[info\] Client transport closed { metadata: undefined }
2025-11-11T07:05:38.195Z \[gladys\] \[info\] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log. { metadata: undefined }
2025-11-11T07:05:38.196Z \[gladys\] \[error\] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) { metadata: { context: ‹ connection ›, stack: undefined } }
2025-11-11T07:05:38.198Z \[gladys\] \[info\] Client transport closed { metadata: undefined }

Main file

2025-11-11 08:05:32 [info] Starting app {
  appVersion: '1.0.332',
  isPackaged: true,
  platform: 'win32',
  arch: 'x64',
  nodeVersion: '22.19.0'
}
2025-11-11 08:05:32 [info] Starting app {
  appVersion: '1.0.332',
  isPackaged: true,
  platform: 'win32',
  arch: 'x64',
  nodeVersion: '22.19.0'
}
2025-11-11 08:05:33 [info] Update URL: https://downloads.claude.ai/releases/win32/x64
2025-11-11 08:05:33 [info] App is installed, enabling initial check and auto-updates
2025-11-11 08:05:33 [info] Checking for updates
2025-11-11 08:05:35 [info] Starting periodic extension update checks (interval: 21600000ms)
2025-11-11 08:05:35 [info] Checking 0 extensions via can_install API using stored metadata
2025-11-11 08:05:35 [info] can_install check completed: 0 extensions checked: [ [length]: 0 ]
2025-11-11 08:05:36 [info] Organization allowlist enabled: false
2025-11-11 08:05:36 [info] Updated allowlist enabled state: false
2025-11-11 08:05:36 [info] Successfully fetched blocklist from https://claude.ai/api/organizations/ef6f458a-e535-4985-8e61-0f656f4ab676/dxt/blocklist with 0 entries
2025-11-11 08:05:36 [info] Saved 1 blocklists with 0 entries
2025-11-11 08:05:36 [info] Successfully updated blocklist
2025-11-11 08:05:37 [info] MCP Server connection requested for: gladys
2025-11-11 08:05:37 [info] Launching MCP Server: gladys
2025-11-11 08:05:37 [info] Checking if UtilityProcess should be used for extension gladys
2025-11-11 08:05:37 [warn] UtilityProcess Check: Extension gladys not found in installed extensions
2025-11-11 08:05:37 [info] Starting app {
  appVersion: '1.0.332',
  isPackaged: true,
  platform: 'win32',
  arch: 'x64',
  nodeVersion: '22.19.0'
}
2025-11-11 08:05:37 [info] Starting app {
  appVersion: '1.0.332',
  isPackaged: true,
  platform: 'win32',
  arch: 'x64',
  nodeVersion: '22.19.0'
}
2025-11-11 08:05:37 [info] Update URL: https://downloads.claude.ai/releases/win32/x64
2025-11-11 08:05:37 [info] App is installed, enabling initial check and auto-updates
2025-11-11 08:05:37 [info] Checking for updates

For info, I used Mistral successfully.

8

Hi @Francis66,

I took the liberty of editing your message to add code tags, it’s more readable that way :slight_smile:

I don’t know much about Windows, but it looks very much like a path issue.

I asked ChatGPT what it recommends, and it suggests either to use:

"C:/Users/franc/.local/bin/mcp-proxy.exe"

Or:

"C:\\Users\\franc\\.local\\bin\\mcp-proxy.exe"

But you shouldn’t mix the two styles.

(Windows users, tell me if I’m talking nonsense)