Your Claude Context is Drowning in Unused Tools

Every enabled MCP server bloats your context window with tool definitions. Just 10 servers can consume 200,000+ tokens—your entire context budget—before you even start working.

10 servers 200k+ tokens consumed
~700 tokens Per tool on average
Budget exhausted Before your first prompt

The Context Window Problem

Each MCP tool consumes ~600-800 tokens on average. An average server has 20-30 tools (~20,000 tokens). Large servers like google_workspace have 90+ tools consuming 60,000+ tokens. With just 10 servers enabled, you're easily consuming 200,000-250,000 tokens—exceeding your entire context budget before your first prompt.

Massive Token Waste

Each tool: ~700 tokens. Average server: 20-30 tools = 20,000 tokens. 10 servers = 200k+ tokens consumed before you start.

Context Overflow

Budget exhausted or exceeded before your code. Large servers (60-100+ tools) can consume 50k-85k tokens each.

Severe Performance Impact

Processing hundreds of unused tool definitions slows every response and dramatically inflates costs.

Debugging authentication? You need 0 MCP servers. Yet with 10 enabled, Claude is burning 200k+ tokens on cryptocurrency APIs, router configs, and web scrapers.

Claude Code MCP Server Selector: Context Window Optimization

A fast, beautiful TUI that lets you enable only the MCP servers you need, when you need them. Disable 10 servers → reclaim 200k+ tokens. Enable only the 1-3 servers for your current task. Toggle with a keypress and launch Claude with an optimized context window—all in under a second.

Instant Control

Sub-second launch. Toggle any server on/off with SPACE. Save and launch with ENTER.

Minimal Context

Enable only 1-3 servers per task. Reclaim 100k-200k+ tokens for your code, not unused tool definitions.

Safe by Design

Atomic updates, automatic backups, explicit consent for changes. Never corrupt your config.

See It In Action

MCP Server Selector TUI Demo

Interactive TUI powered by fzf - toggle servers instantly with visual feedback

Features

Context Optimization

Enable only the servers you need. Minimize token waste and maximize effective context for your work.

Interactive TUI

Fast, intuitive interface powered by fzf. Navigate, filter, and toggle with keyboard shortcuts.

Real-time Updates

Toggle servers instantly with visual feedback. Preview window shows current vs pending state.

Multi-Source Config

Discovers and merges 7 configuration sources with smart scope precedence (local → project → user).

Smart Migration

Automatically migrate global servers to project-level control with backup and rollback protection.

Safe by Design

Atomic writes, automatic backups, JSON validation. Explicit consent before global changes.

Your New Workflow

Optimize your context in seconds, every time you start a new task

1

Exit Claude Code

If Claude is currently running, exit to refresh with new settings

2

Run claudemcp

Launch the TUI in your project directory

3

Enable What You Need

Press SPACE to toggle. Only enable 1-3 servers for your current task (most tasks need 0-1)

4

Launch & Work

Press ENTER to save and auto-launch Claude with optimized context

Pro tip: Most tasks need 0-1 servers. Working on web APIs? Enable fetch (1 server, ~800 tokens). Debugging timezones? Enable time (1 server, ~600 tokens). Everything else? Disable all servers and reclaim 200k+ tokens.

Get Started

One-Line Install

curl -fsSL https://raw.githubusercontent.com/henkisdabro/Claude-Code-MCP-Server-Selector/main/install.sh | bash

The installer will check for dependencies (fzf, jq) and set up symlinks automatically.

Usage

mcp Short command
claudemcp Descriptive command (same functionality)

Keybindings

SPACE Toggle server on/off
ENTER Save changes & launch Claude
ESC Cancel without saving
Ctrl-A Add new server
Ctrl-X Remove selected server
Alt-E Enable all servers
Alt-D Disable all servers
↑/↓ or / Navigate & filter

Free for the Claude Code Community

Open source and MIT licensed. Built to solve a real problem for developers like you.