HTTP MCP Server with Claude Desktop

[KingKoontz]

Hi,

I have installed the MCP Server on an Azure App Service, with Transport_Mode = http.
It's ok, the server is enabled, and it's ok when I test with the shell on the server.

But now, I want to test access with Claude Desktop on my local machine.

So I try to add a config:
{
"mcpServers": {
"ashari-confluence": {
"type": "http",
"url": "https://***.azurewebsites.net/mcp",
"command": ""
}
}
}

If I don't put the command parameter, I had an error. So I try with this parameter, but it doesn"t work :'(

2025-09-09T15:09:16.789Z [ashari-confluence] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0} { metadata: undefined }
2025-09-09T15:09:16.784Z [ashari-confluence] [info] Server started and connected successfully { metadata: undefined }
2025-09-09T15:09:16.809Z [ashari-confluence] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0} { metadata: undefined }
'.' n'est pas reconnu en tant que commande interne
ou externe, un programme ex cutable ou un fichier de commandes.
2025-09-09T15:09:16.962Z [ashari-confluence] [error] spawn ENOENT {
metadata: {
context: 'connection',
stack: 'Error: spawn ENOENT\n' +
' at e (C:\Users\\AppData\Local\AnthropicClaude\app-0.12.129\resources\app.asar\.vite\build\index.js:213:7433)\n' +
' at n (C:\Users\\AppData\Local\AnthropicClaude\app-0.12.129\resources\app.asar\.vite\build\index.js:213:7760)\n' +
' at a.emit (C:\Users\***\AppData\Local\AnthropicClaude\app-0.12.129\resources\app.asar\.vite\build\index.js:213:7651)\n' +
' at ChildProcess._handle.onexit (node:internal/child_process:293:12)'
}
}
2025-09-09T15:09:16.962Z [ashari-confluence] [info] Server transport closed { metadata: undefined }
2025-09-09T15:09:16.963Z [ashari-confluence] [info] Client transport closed { metadata: undefined }
2025-09-09T15:09:16.964Z [ashari-confluence] [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-09-09T15:09:16.964Z [ashari-confluence] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation { metadata: { context: 'connection', stack: undefined } }
2025-09-09T15:09:16.964Z [ashari-confluence] [info] Client transport closed { metadata: undefined }
'.' n'est pas reconnu en tant que commande interne
ou externe, un programme ex cutable ou un fichier de commandes.

What is the good config to access the MCP server in http with Claude Desktop?

[aashari]

Hi @KingKoontz,

This is a limitation of Claude Desktop rather than this MCP server. Claude Desktop currently only supports STDIO transport for MCP servers - it spawns a local process and communicates via stdin/stdout.

For Claude Desktop, you must use STDIO mode (the default):

{
  "mcpServers": {
    "confluence": {
      "command": "npx",
      "args": ["-y", "@aashari/mcp-server-atlassian-confluence"],
      "env": {
        "ATLASSIAN_SITE_NAME": "your-company",
        "ATLASSIAN_USER_EMAIL": "your.email@company.com",
        "ATLASSIAN_API_TOKEN": "your_api_token"
      }
    }
  }
}

HTTP transport is designed for:

• Web-based integrations
• Testing with MCP Inspector (npm run mcp:inspect)
• Custom applications that can make HTTP requests

If you need to access a remote Confluence instance from Claude Desktop, the credentials are passed via environment variables - Claude Desktop will spawn the MCP server locally, and that local server will make authenticated API calls to your Confluence Cloud instance (even if it's on Azure).

The error you're seeing (spawn ENOENT) is because Claude Desktop is trying to spawn a process with an empty command string, which fails.

Hope this helps clarify the architecture!