{"version":"2.1.295","anchor":"pushed-mcp-server-url-length-limit-documented-4096-chars","canonical_anchor":"pushed-mcp-server-url-length-limit-documented-4096-chars","heading":"Refused pushed MCP servers now see a 4,096-character URL limit","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/pushed-mcp-server-url-length-limit-documented-4096-chars","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Refused pushed MCP servers now see a 4,096-character URL limit\n\nThe message refusing a pushed MCP server now says its URL can be at most 4,096 characters\n\n**What**\n\nMCP (Model Context Protocol) servers connect Claude Code to outside tools and data. A server can be pushed into a session, and Claude Code refuses one that does not meet its rules. The refusal message used to say only that a pushed server must be an http server on the session's MCP proxy route. It now also says the URL can be at most 4,096 characters.\n\nWhen counting, a non-ASCII character, such as an accented letter, counts as the number of bytes it takes once percent-encoded. Percent-encoding is how URLs write such characters, so one character can count as several.\n\n**Why**\n\nA pushed MCP server with a long URL will be refused. If yours contains many non-ASCII characters, it reaches the limit sooner than its visible length suggests.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}