{"version":"2.1.283","anchor":"context-shows-mcp-server-instructions-as-a-separate-categor","canonical_anchor":"context-shows-mcp-server-instructions-as-a-separate-categor","heading":"\/context lists MCP server instructions as their own category","tier":"use","area":"Context","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/context-shows-mcp-server-instructions-as-a-separate-categor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `\/context` lists MCP server instructions as their own category\n\nThe `\/context` breakdown now shows how much of the context MCP server instructions take up, next to MCP tools\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools, and they can send instructions that are added to the conversation. The context usage breakdown now counts those instructions, including instruction blocks added on your side, and shows them as \"MCP server instructions\" beside \"MCP tools\". Before, they had no line of their own.\n\nThe count is 0 when `CLAUDE_CODE_DISABLE_ATTACHMENTS` or `CLAUDE_CODE_SIMPLE` is set.\n\n**Why**\n\nYou can see how much room lengthy MCP server instructions use, which helps when deciding which servers to keep.\n\n- Area: Context\n- Names: `\/context`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}