{"version":"2.1.239","anchor":"mcp-servers-can-be-put-in-their-own-memory-cgroup-on-linux","canonical_anchor":"mcp-servers-can-be-put-in-their-own-memory-cgroup-on-linux","heading":"MCP servers can be put in their own memory cgroup on Linux","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/mcp-servers-can-be-put-in-their-own-memory-cgroup-on-linux","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### MCP servers can be put in their own memory cgroup on Linux\n\nOn Linux you can force MCP servers into their own memory cgroup with an environment variable.\n\n**What**\n\nOn Linux, MCP server processes and up to 256 of their discovered child processes can be attached to a dedicated `mcp` control group so their memory is accounted separately from Claude Code's. Off unless the `tengu_mcp_memory_cgroup` flag is on (its fallback is false); `CLAUDE_CODE_MCP_MEMORY_CGROUP` forces it on, and a falsy value or `none` disables it.\n\n**Details**\n\n- Processes spawned before the flag resolves are parked and attached once it does.\n- Reports a `tengu_mcp_cgroup` event with status enabled or disabled, plus `mcp_memory_cgroup` failure reasons.\n\n**Evidence**\n\n`tengu_mcp_memory_cgroup`\n\n- Flag `tengu_mcp_memory_cgroup`: Off in both readings (read for one account on one subscription tier against v2.1.239; this account: off, anonymous baseline: off, compiled default: off)\n- Area: MCP\n- Names: `CLAUDE_CODE_MCP_MEMORY_CGROUP`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}