Key takeaways

  • Run /context in Claude Code to see what is using your context window.
  • Toggle a server off in /mcp to disable it and keep its configuration, or run claude mcp remove <name> to delete it.
  • MCP tool definitions are deferred by default, so an idle server costs little on current models.

To remove tools from Claude Code and free up space, run /context to see what is using your context window, then run /mcp to switch off any server you are not using, or claude mcp remove <name> in your shell to delete it for good. That is how to remove tools in Claude Code to free up space, according to Anthropic's MCP documentation and its cost guide. Both pages were read on November 4, 2026.

"Tools" here means MCP servers, the add-ons that give Claude Code access to services such as Notion or Sentry. This guide covers Claude Code, the command-line tool. The docs don't describe a separate way to remove tools in the Claude chat apps.

What you need

  • Claude Code installed, with at least one MCP server configured.
  • A session open at the Claude Code prompt for the / commands, and a normal shell for the claude mcp commands.

I did not run these commands in the VM. Everything below comes from the two pages named above.

How much space tools use now

Tool definitions are deferred by default. The MCP docs say that only tool names and server instructions load at session start, and Claude pulls in a tool's full definition when it needs it. So an idle server costs little. Anthropic's cost guide still lists disabling unused servers as a way to cut context use.

Deferral has exceptions. Models older than Claude Opus 4 and Sonnet 4 load all MCP tools upfront, as do deployments on Microsoft Foundry hosted on Azure, and sessions where ENABLE_TOOL_SEARCH=false is set. On those setups, removing a server frees more.

How to see what is using space

Run /context at the Claude Code prompt. The cost guide says it shows what is consuming space. The MCP docs add that /context labels tools (deferred) or (loaded on-demand) when tool search is handling them.

To check the status of your servers, run /mcp inside Claude Code, or claude mcp list in your shell. claude mcp get <name> shows the details of one server.

How to turn a server off without deleting it

  1. Run /mcp in Claude Code.
  2. Select the server and toggle it off.

Per the docs, this stops Claude Code from connecting to the server and keeps its configuration. The server stays in the /mcp list, marked Disabled for this project (re-enable via /mcp). The choice is saved per project in ~/.claude.json under disabledMcpServers. A claude.ai connector you disable this way is saved there under its display name, such as claude.ai Slack.

If a server comes from a project's .mcp.json file and you want it blocked in every permission mode, add it to the disabledMcpjsonServers setting, which is described in the settings reference.

How to remove a server for good

In your shell, run:

claude mcp remove notion

Replace notion with the name shown by claude mcp list. For a project-scoped server, add the scope: claude mcp remove <name> --scope <scope>.

When you remove a remote server, Claude Code also deletes the OAuth tokens and client registration it stored for it. It does not revoke the tokens at the service that issued them. If that service supports revocation, run claude mcp logout <name> before claude mcp remove <name>.

A server that came from a plugin is not removed with these commands. The docs say you add and remove plugin servers by installing or uninstalling the plugin. You can still toggle an installed plugin's server off in /mcp.

Other ways to free up space

  • Start fresh between unrelated tasks with /clear. Run /rename first if you want to find the session again with /resume.
  • Run /compact with instructions, for example /compact Focus on code samples and API usage, to summarize the conversation and keep what matters.
  • Use a command-line tool such as gh, aws or gcloud instead of an MCP server where one exists. The cost guide says these add no per-tool listing.
  • Keep CLAUDE.md under 200 lines, and move workflow-specific instructions into skills, which load only when invoked.
  • To keep only chosen servers for one run, start Claude Code with --strict-mcp-config and pass your servers with --mcp-config.

Tool search settings

The ENABLE_TOOL_SEARCH environment variable controls deferral. With it unset, all MCP tools are deferred. auto loads tools upfront while their definitions take under 10% of the context window. auto:5 sets the threshold to 5%. false loads every MCP tool upfront.

ENABLE_TOOL_SEARCH=auto:5 claude

A server entry can also set alwaysLoad to true so its tools are never deferred. Each upfront tool takes context, so the docs suggest it only for a few tools Claude needs on every turn. Setting "alwaysLoad": false keeps a server's tools deferred, from Claude Code v2.1.287.

Where to go next

Our guide to how to check token usage in Claude shows how to keep an eye on the context window while you work.

Frequently asked questions

How do I remove an MCP server in Claude Code?

Run claude mcp remove followed by the server name in your shell. Use claude mcp list to see the names. For a plugin's server, uninstall the plugin instead.

How do I disable a tool without deleting it?

Open /mcp in Claude Code and toggle the server off. The server stays listed as disabled for this project, and you can re-enable it from the same panel.

How do I see what is using my Claude Code context?

Run /context. Anthropic's cost guide points to it for seeing what is consuming space.

Do unused MCP tools fill my context window?

Less than before. Tool definitions are deferred by default, so only tool names and server instructions load at session start. Older models and some setups load all tools upfront.

Sources

  1. Connect Claude Code to tools via MCPAnthropic
  2. Manage costs effectivelyAnthropic