Skip to content

fix(mcp): NDJSON framing for azure-monitor-mcp - #9

Merged
vitorcastro78 merged 2 commits into
mainfrom
dynamic-context-discovery
Aug 30, 2026
Merged

vitorcastro78 merged 2 commits into
mainfrom
dynamic-context-discovery

Conversation

@vitorcastro78

Copy link
Copy Markdown
Collaborator

Summary

  • Align azure-monitor-mcp stdio framing with ContextMemory mcp-runtime (NDJSON write; dual NDJSON + Content-Length read).
  • Fixes production catalog rebuild timeout: MCP request timed out: initialize after 120000ms.

Test plan

  • Local smoke: NDJSON initialize + tools/list returns 3 tools
  • After deploy-local: POST mcp/catalog/rebuild with integrationName=azure-monitor succeeds
  • GET mcp/servers shows azure-monitor Success=true ToolCount=3

mcp-runtime hosts stdio as line-delimited JSON; Content-Length-only framing caused initialize to hang until the 120s timeout.
@vitorcastro78
vitorcastro78 merged commit 0e6163a into main Aug 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants