{"version":"2.1.275","anchor":"bridge-meta-mcp-mount-internal-rename-only","canonical_anchor":"bridge-meta-mcp-mount-internal-rename-only","heading":"Bridge meta-MCP mount: internal rename only","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/bridge-meta-mcp-mount-internal-rename-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Bridge meta-MCP mount: internal rename only\n\nInternal rename of the dynamic-MCP bridge server code, no behavior change\n\n**What**\n\nThe module that manages the \"meta-MCP\" bridge (the internal server config used to mount dynamically connected MCP servers, a way of plugging in external tool servers) had its internal variables and helper functions renamed throughout, including its permission set\/get wrapper, allow\/deny rule helpers, and mount connect\/detach logic.\n\n**Why**\n\nThis is a code-clarity change only; nothing about how the bridge behaves appears to have changed.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}