Describe the bug
When configuring and running the Azure MCP server (both Node.js and Python variants), the MCP client fails to communicate with the server.
Although the server starts without engine/version errors, any tool invocation results in a connection failure with a JSON parsing error.
This appears to indicate that the MCP server is either:
emitting non-JSON output on stdout, or
closing the connection prematurely during MCP protocol communication
Expected behavior
MCP server should successfully initialize via stdio
MCP client should be able to call tools without connection termination
Responses should be valid JSON-RPC messages as per MCP protocol
Actual behavior
On tool invocation, the following error occurs:
Failure in MCP tool execution: connection closed: calling "tools/call": client is closing: invalid character 'X' looking for beginning of value
This happens consistently across both Node and Python implementations.
Reproduction Steps
- Configure MCP server (Node version):
{
"mcpServers": {
"azure-mcp": {
"command": "/home/bharat/.nvm/versions/node/v22.21.1/bin/node",
"args": [
"/home/bharat/.nvm/versions/node/v22.21.1/bin/azmcp",
"server",
"start"
]
}
}
}
- Alternatively, configure using Python (
uvx):
{
"mcpServers": {
"Azure MCP Server": {
"command": "uvx",
"args": [
"--from",
"msmcp-azure",
"azmcp",
"server",
"start"
]
}
}
}
- Start Antigravity and ask question regarding azure enviorment like, what are all the function apps in my subscription.
- Observe failure
Environment
-
MCP Client: Antigravity
-
OS: Ubuntu (Latitude 5480)
-
Node.js: v22.21.1
-
npm: 10.9.4
-
Python: (via uvx, version can be added if needed)
-
MCP Client: (please specify — e.g., Cursor / Claude Desktop / VS Code MCP extension)
-
Azure MCP package:
- Node:
@azure/mcp@latest
- Python:
msmcp-azure
Describe the bug
When configuring and running the Azure MCP server (both Node.js and Python variants), the MCP client fails to communicate with the server.
Although the server starts without engine/version errors, any tool invocation results in a connection failure with a JSON parsing error.
This appears to indicate that the MCP server is either:
emitting non-JSON output on stdout, or
closing the connection prematurely during MCP protocol communication
Expected behavior
MCP server should successfully initialize via stdio
MCP client should be able to call tools without connection termination
Responses should be valid JSON-RPC messages as per MCP protocol
Actual behavior
On tool invocation, the following error occurs:
This happens consistently across both Node and Python implementations.
Reproduction Steps
{ "mcpServers": { "azure-mcp": { "command": "/home/bharat/.nvm/versions/node/v22.21.1/bin/node", "args": [ "/home/bharat/.nvm/versions/node/v22.21.1/bin/azmcp", "server", "start" ] } } }uvx):{ "mcpServers": { "Azure MCP Server": { "command": "uvx", "args": [ "--from", "msmcp-azure", "azmcp", "server", "start" ] } } }Environment
MCP Client: Antigravity
OS: Ubuntu (Latitude 5480)
Node.js: v22.21.1
npm: 10.9.4
Python: (via
uvx, version can be added if needed)MCP Client: (please specify — e.g., Cursor / Claude Desktop / VS Code MCP extension)
Azure MCP package:
@azure/mcp@latestmsmcp-azure