{"version":"2.1.323","anchor":"mcp-servers-can-be-scoped-to-a-project-instead-of-always-dyn","canonical_anchor":"mcp-servers-can-be-scoped-to-a-project-instead-of-always-dyn","heading":"MCP servers loaded from a source can now count as project servers","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-servers-can-be-scoped-to-a-project-instead-of-always-dyn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP servers loaded from a source can now count as project servers\n\nMCP servers loaded from a known folder are now marked with project scope instead of always being marked dynamic\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools, and each one has a scope that says where it came from. When Claude Code can tell which folder a server's configuration was read from, it now marks the server with project scope and records that folder. Otherwise it marks it dynamic. Before, these servers were always marked dynamic.\n\n**Why**\n\nThis changes where Claude Code says an MCP server came from, which can affect how it is listed and treated.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}