If you run more than a couple of MCP servers in Claude Code, you've probably hit
the loaded-tools warning (~40 tools). The usual fix is manually enabling/disabling
servers by hand every time your task changes, and remembering which tools depend
on which.
mcp-profile
is a small, dependency-free CLI (+ a Claude Code skill) that lets
you define named profiles — e.g. "research", "coding", "deploy" — each listing
the MCP servers that task actually needs, then switch between them with one
command:
mcp-profile use research
It edits the same enabledMcpjsonServers
/ disabledMcpjsonServers
fields
Claude Code already reads — no new config format, no daemon, no account, no
network calls. MIT licensed.
Repo: https://github.com/pozga/mcp-profile
Feedback wanted: does this match how you're actually hitting the tool-count
problem? What would make this worth paying for (team-shared profiles? a
dashboard?) vs. just a free utility?