{"version":"2.1.318","anchor":"new-mcp-server-config-field-urlreportable","canonical_anchor":"new-mcp-server-config-field-urlreportable","heading":"claude.ai connectors can be marked urlReportable","tier":"use","area":"Connectors","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/new-mcp-server-config-field-urlreportable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### claude.ai connectors can be marked urlReportable\n\nclaude.ai connector configs gain an optional urlReportable field, passed through when the server reports url_reportable as true\n\n**What**\n\nA connector is an outside service that Claude can use through MCP (Model Context Protocol, the standard Claude Code uses to talk to add-on tools and services). Connectors set up on claude.ai can now carry a new setting.\n\n- `urlReportable` is a new optional true\/false field in the claude.ai connector schema.\n\n- MCP servers reached through the claude.ai proxy (`claudeai-proxy`) now have `urlReportable` set to true in their config when the server reports `url_reportable` as true. Otherwise the field is left out.\n\n**Why**\n\nThe field marks whether a connector's server address may be reported. The members do not show what reads it, so for now it is a new piece of information that travels with claude.ai connectors and does not change how they behave.\n\n- Area: Connectors\n- Names: `urlReportable`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}