{"version":"2.1.274","anchor":"mcp-server-identity-now-threaded-through-permission-requests","canonical_anchor":"mcp-server-identity-now-threaded-through-permission-requests","heading":"MCP server identity now threaded through permission requests","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-server-identity-now-threaded-through-permission-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### MCP server identity now threaded through permission requests\n\nPermission prompts now carry which MCP server is asking, including its name and source\n\n**What**\n\nAn MCP server is an external tool provider Claude Code can connect to. Permission requests (the prompts asking whether Claude Code may use a tool) can now include an optional `mcp_server` field with `name` and `source`, which is validated and stripped out with a warning if malformed. This information is also passed through to the permission dialog shown to the user, and to the tools that check request formatting.\n\n**Why**\n\nWhen a permission request comes from an MCP-provided tool, the person approving it can now see which MCP server is making the request, rather than seeing only the tool name with no indication of which external server it came from.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}