KyttoMCP

KyttoMCP

**A local control panel for MCP servers across the AI clients you already use.**

[](https://github.com/heyitsjakub/KyttoMCP/releases) [](https://kytto.jakubhecht.sk/) [](https://kytto.jakubhecht.sk/)

[**Download Beta 1.0.5**](https://kytto.jakubhecht.sk/) · [Website](https://kytto.jakubhecht.sk/) · [Changelog](CHANGELOG.md) · [Report a bug](https://kytto.jakubhecht.sk/#report-bug)

---


See it work — 72 seconds, no narration

https://github.com/user-attachments/assets/e8e91309-8f4a-4ba5-9a1d-ac306b51d664

Eleven MCP servers across four clients, one of them refusing to start. Kytto switches a server on for Claude Code, shows the stderr behind the failing one, and measures what each server costs in context. Recorded unedited on Windows with Beta 1.0.2 — [also on the site](https://kytto.jakubhecht.sk/#demo).

The problem

Once you run more than two or three MCP servers, the configuration is spread across files that share nothing but the idea:

~/.claude.json                 Claude Desktop / Claude Code
~/.cursor/mcp.json             Cursor
settings.json                  VS Code
config.toml                    Codex

Different formats, different locations, different rules about what a valid entry looks like. And the question that keeps coming back has no single place to answer it: **what is actually enabled, where?**

What Kytto does

Kytto reads those files locally and turns them into one workspace.

**See and change what is enabled** Every server against every client in one matrix. Toggle a server on or off, edit a definition across every client that uses it, or remove it from one client without to