{"version":"2.1.319","anchor":"mcp-relay-allows-server-initiated-request-methods","canonical_anchor":"mcp-relay-allows-server-initiated-request-methods","heading":"The MCP relay may pass requests from servers back to Claude Code","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-relay-allows-server-initiated-request-methods","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### The MCP relay may pass requests from servers back to Claude Code\n\nThe MCP relay can now pass through more methods, with a list naming elicitation, sampling and roots requests from servers\n\n**Unclear.** It is not confirmed that the three named server requests are among the methods now passed through.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. The relay is a path that carries messages between them. It used to pass on only one set of message types, called methods. It now passes on a second set as well.\n\nA list naming `elicitation\/create`, `sampling\/createMessage` and `roots\/list` was also added. These are requests a server makes to Claude Code, for example asking you a question. Tool calls are still checked before they are passed on.\n\n**Why**\n\nMore kinds of MCP message can now go through the relay.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}