Skip to content

Fix bc-mcp-proxy protocol version mismatch with BC#347

Open
vignirvignir wants to merge 2 commits intomicrosoft:masterfrom
vignirvignir:fix/bc-mcp-proxy-protocol-version
Open

Fix bc-mcp-proxy protocol version mismatch with BC#347
vignirvignir wants to merge 2 commits intomicrosoft:masterfrom
vignirvignir:fix/bc-mcp-proxy-protocol-version

Conversation

@vignirvignir
Copy link

Summary

  • Business Central's MCP server only accepts protocolVersion: "2024-11-05", but MCP SDK 1.21+ sends "2025-11-25" by default, causing HTTP 400 responses
  • Temporarily override mcp.types.LATEST_PROTOCOL_VERSION to "2024-11-05" before the initialize() handshake, then restore it afterward
  • Bump version to 0.1.3

Test plan

  • Run bc-mcp-proxy with MCP SDK >=1.21.0 against a BC SaaS environment and verify the initialize handshake succeeds
  • Confirm debug logs show Connected to remote MCP server (protocol 2024-11-05)
  • Verify tool listing and tool calls still work end-to-end through the proxy

🤖 Generated with Claude Code

Override MCP SDK's default protocol version ("2025-11-25") to "2024-11-05"
during the initialize handshake, since Business Central's MCP server only
accepts the older protocol version. Bump version to 0.1.3.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vignirvignir
Copy link
Author

@microsoft-github-policy-service agree

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

1 participant