{"version":"2.1.315","anchor":"mcp-servers-ignored-in-remote-workspace-with-warnings","canonical_anchor":"mcp-servers-ignored-in-remote-workspace-with-warnings","heading":"Remote sessions explain that --mcp-config, agent MCP servers and --chrome are ignored","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-servers-ignored-in-remote-workspace-with-warnings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions explain that --mcp-config, agent MCP servers and --chrome are ignored\n\nIn remote sessions, a warning now says MCP servers from --mcp-config or agent frontmatter are ignored and that --chrome has no effect\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. In a remote session, Claude Code works in a workspace on another machine. MCP runs in that remote workspace, so servers you set up on your own machine are not used. The warning about this changed:\n\n- It says that servers from `--mcp-config` or from agent frontmatter are ignored because \"MCP runs in the remote workspace\". Agent frontmatter is the settings block at the top of an agent file.\n\n- It also warns that `--chrome`, the option for Chrome browser integration, has no effect in that case.\n\n- One helper now builds the warning from `mcpConfigFlagServers`, the agent, the chrome flag and `dynamicMcpConfig`. Before, the warning was built inline for every dynamic MCP server and only mentioned `--mcp-config` and agent frontmatter.\n\n**Why**\n\nIf you pass `--mcp-config` or `--chrome` to a remote session, you now get a warning that these options do nothing there. The wording of the warning, and which servers it lists, may differ from before.\n\n- Area: Sessions\n- Names: `--chrome`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}