{"version":"2.1.290","anchor":"mcp-transport-label-ccr-toolport","canonical_anchor":"mcp-transport-label-ccr-toolport","heading":"New ccr-toolport connection mode for HTTP MCP servers","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-transport-label-ccr-toolport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### New ccr-toolport connection mode for HTTP MCP servers\n\nHTTP MCP servers that match a toolport address are now marked `ccrToolport` and labelled `ccr-toolport`, ahead of the older `ccr-proxy` label\n\n**What**\n\nMCP servers are outside programs that add tools to Claude Code, and some are reached over HTTP. Claude Code has a new way to classify how it connects to them.\n\n- The step that decides an MCP server's connection mode now receives a `ccrToolport` value. It is true for HTTP servers whose address passes a toolport check. Before, only `inProcess` and `ccrProxy` were passed.\n\n- When `ccrToolport` is set, the connection is labelled `ccr-toolport`. This takes precedence over `ccr-proxy` for HTTP servers. Before, the choice was only between `ccr-proxy` and `http`.\n\n**Why**\n\nThis adds a separate route for certain HTTP MCP servers. It shows up as its own `ccr-toolport` label instead of being grouped under `ccr-proxy` or plain `http`.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}