Inspect it.
Both apps, the issue tracker and the release history are public on GitHub. There is no account, no cloud sync and no telemetry, and you can check that in the code.
macOS & Windows · Beta 1.0.7.1
See every MCP server
in every AI client.
A desktop app that reads the MCP config files already on your computer — across Claude Desktop, Claude Code, Cursor, VS Code and Codex — and shows every server and client in one matrix. Nothing to migrate, nothing sitting between your clients and your tools.
Open sourceMIT License · read every line on GitHub ↗- Free to use
- No account required
- No migration — reads your existing configs
- Runs locally — your configs never leave your computer
Any MCP server you already run — in the clients you already useClaude DesktopClaude CodeCursorVS CodeCodex
Open source · MIT License
Read every line
before you run it.
Kytto reads the config files where your servers and their API keys live, so you should be able to inspect it. The source of both the macOS and the Windows app is public under the MIT License.
Build it yourself.
The macOS app builds from source with one script, macos/scripts/make-dmg.sh, and no Apple developer account. The installers are not signed, so building the app from source you have read is a real alternative to trusting a download.
Verify the download.
Release builds are published on GitHub, and the SHA-256 checksums are printed in the download section so you can compare the file you received.
Browse the source on GitHub ↗ · MIT License ↗ · Public issues ↗
The problem Kytto solves
MCP gets powerful.
The setup gets messy.
Once you use several servers across several clients, the same question keeps coming back: what is enabled where?
Kytto reads those scattered JSON and TOML configurations and turns them into one dependable workspace — with health checks, profiles, backups, and a clear path back when you need it.
Stop asking “is it enabled here?”
See your servers and supported clients together in one matrix. Change the client you choose while keeping its own configuration rules.
Find out why a server fails.
A missing environment value, a relative path that only resolves in one client, an executable that is not on that client’s PATH, a handshake that never completes. Inspect the handshake and let MCP Doctor name the cause.
Keep a setup for each task.
Save Coding, Research or Minimal profiles. Preview a change before applying it, with backups available if you need to go back.
Already have servers configured? Nothing changes. Kytto reads the config files you have now — your own servers, ones from npm, anything already in the file — and writes back to those same files in each client’s own format. There is no Kytto format to convert to and no gateway you are required to route through. Comparing ways to manage your setup? See where Kytto fits →
See it work · 72 seconds
One real setup,
start to finish.
Watch a server switch on for Claude Code, investigate a failed connection, and compare estimated tool-schema footprints — in one unedited recording.
Explore all 10 features in Beta 1.0.7.1
One matrix. Every client.
See where each server is active across Claude Desktop, Claude Code, Cursor, VS Code and Codex. Switch servers on or off from one view while Kytto respects each client’s own rules.
Built-in and custom sources.
Create MCP entries manually or start from Kytto’s built-in catalog. Attach named JSON, JSONC or TOML files as read-only sources without confusing them with writable clients.
Health you can inspect.
Run an on-demand MCP handshake and see tools, prompts, resources, protocol details, stderr, and token-weight estimates instead of guessing why a server is failing.
Profiles for focused setups.
Save local MCP stacks such as Coding, Research or Minimal. Preview what will change, then apply a profile to one client with the normal backup and restart safeguards.
Secrets, without the surprise.
Find sensitive environment values while keeping them masked by default. Reveal on request, rotate one value everywhere it appears, keep an optional Keychain copy, or restrict config permissions.
A visible way back.
Every write checks for external changes, makes a timestamped backup, and writes atomically. Browse backups in Kytto and restore an earlier configuration with the replaced version backed up too.
Optional Gateway mode.
For supported stdio servers, preview a local Gateway route, move the direct definition and credentials into native storage, and restore Direct mode with one click.
Context optimizer.
Measure the estimated full-schema footprint of each server and profile. It is a consistent size comparison, not exact per-conversation usage; clients differ in how and when they load tool definitions. Where a client has a documented tool limit, such as 128 tools in VS Code, Kytto shows how close you are to it.
MCP Doctor.
Turn config and health evidence into actionable findings — from missing environment values and relative paths to failed handshakes and executables that depend on a client’s PATH, plus packages started without an exact version, which it can pin, and a safety scan of what each tool tells the model. Safe fixes are previewed before writing.
Live Activity, kept private.
Review Gateway sessions, tool calls, latency and failures, export a safe support report, and see Contract Guard alerts when a server changes what it tells the model. Arguments, results and payloads stay out of the activity log.
The part you never read
A server can change
what it tells your model.
A tool’s name, description and input schema are not documentation — your client hands them to the model as written. That makes them the one part of an MCP server that can instruct your agent without the tool ever being called, and the one part you never see. A single line in a description can tell your agent to read ~/.ssh or pass a key to another tool — and you would never find it in the config. A server you trusted last month can rewrite them tonight: no new version, no update prompt, nothing in the config file to notice.
See the text your model sees.
Kytto reads each tool’s description and schema exactly as the model receives them, then reports what a person reading the same screen would have missed:
- Invisible charactersText in the model’s copy that is not in yours.
- Wording that instructs the modelA description addressing the agent instead of describing a tool.
- Imitated system messagesMarkup pretending to carry developer authority.
- Credential interestA read-only tool naming keys or secrets by name.
- Shadowed tool namesTwo enabled servers claiming the same name in one client.
Deliberately narrow, so a finding next to a green dot is worth reading. The scan is advice — it never switches a server off and never edits a configuration.
Get told when it changes.
Contract Guard remembers what each server said last time. After a health check it compares the model-visible contract against the one it saw before and grades what moved:
- Tool removed · input schema changedBreaking
- Description or safety annotation changedWarning
- New tool addedInfo
Marking a change as reviewed clears the alert and moves the baseline, so the next check compares against what you actually approved.
Kytto 1.0.7 on Windows. drift-fixture is a harmless test server written for this demonstration; the instruction in its description is a sample and does nothing.
Both run locally as part of the health check and MCP Doctor — nothing to switch on, and no server is ever contacted on your behalf. Try it on your own servers →
Designed around trust
Your configuration stays yours.
Kytto works directly with the files already on your computer. There is no cloud account, no sync service, and no secret upload sitting between you and your tools. Gateway activity is metadata-only, with payload capture off.
01Automatic backupsA timestamped copy is made before every change.
02Guarded atomic writesExternal changes are detected before Kytto writes.
03Local by designYour MCP configuration and credentials stay on your computer.
Your first session
Start with the setup you already have.
Review what Kytto found.
Open the app and review the detected workspace before entering the matrix. No migration required.
Pick one server to inspect.
See which clients have it enabled. Run a health check when you want to investigate its connection.
Make a deliberate change.
Choose a client and preview a profile change. Kytto makes a backup before writing to your configuration.
Beta 1.0.7.1 · Available now
Try it with your own setup.
Free and open source. No account or sign-up. Choose macOS or Windows, then follow the first-launch steps below.
This is an unsigned beta, so your system may show a warning. Launch instructions and file checksums are included below, and you can also build it from source. See what’s new in 1.0.7.1 →
FOR MAC
macOS
Universal build. Runs on both Apple Silicon and Intel Macs.
Download for macOS ↓ 1.0.7.1 beta · KyttoMCP-1.0.7.1.dmg · 4.8 MBHow to open it the first time
- Open the downloaded DMG and drag KyttoMCP into Applications.
- In Applications, Control-click or right-click KyttoMCP and choose Open.
- Click Open again. If macOS still blocks it, go to System Settings → Privacy & Security and choose Open Anyway.
FOR PC
Windows
Guided setup installer for Windows.
Download for Windows ↓ 1.0.7.1 beta · Kytto-Setup-win-x64-1.0.7.1.exe · 78.4 MBHow to open it the first time
- Open the downloaded Kytto setup file.
- If Microsoft Defender SmartScreen appears, click More info.
- Choose Run anyway, then follow the installer steps.
Questions
Before you download.
The things people ask most often about the beta. Something missing? Send it through the form below and it gets answered.
What is KyttoMCP?
KyttoMCP is a local control panel for Model Context Protocol servers. It reads the MCP configuration files that already exist on your computer and shows, in one place, which servers are enabled in Claude Desktop, Claude Code, Cursor, VS Code and Codex — so you can inspect, edit and switch them without opening JSON and TOML files by hand.
Is KyttoMCP free?
Yes. Beta 1.0.7.1 is free for macOS and Windows, with no account, no sign-up and no cloud service, and the source code of both apps is public under the MIT License. Everything the beta does runs on your own computer.
Does it only work with servers made by Kytto?
No. Kytto manages any MCP server you already run — Playwright, Filesystem, GitHub, anything from npm or PyPI, a server your team wrote in-house, or one you added to a config file by hand. It reads what is in your configuration files rather than a catalog of its own. The built-in catalog is a shortcut for adding new servers, never a limit on which ones Kytto can see.
Which AI clients does it work with?
Claude Desktop, Claude Code, Cursor, VS Code and Codex. Kytto respects each client’s own configuration format and rules, so changing a server in one client does not silently rewrite another.
Does Kytto upload my configuration or API keys anywhere?
No. Your MCP configuration, your credentials and your project files stay on your computer. There is no cloud sync and no secret upload. Builds up to 1.0.6.3 offered optional anonymous diagnostics, off by default; Beta 1.0.7 removed them, and the site no longer stores anything older builds send. The source code is public, so you can check every request the app makes.
Can Kytto tell me whether an MCP server is safe?
It can tell you things you cannot see by reading the config. During a health check Kytto reads each tool’s description and input schema the way the model receives them and flags invisible characters, wording that instructs the model, imitated system messages, read-only tools that name credentials, and two servers claiming the same tool name. Contract Guard additionally reports when a server changes that text after you installed it, and keeps reporting it until you review the change. These are findings for you to read — Kytto never switches a server off on its own, and a clean scan is not a guarantee that a server is trustworthy.
Why does my Mac or Windows PC warn about an unidentified developer?
Kytto is an independent beta that is not signed with paid Apple and Microsoft developer certificates, so both systems show a caution screen. On macOS, Control-click the app and choose Open. On Windows, choose More info and then Run anyway. Only do this for a file downloaded directly from this page — the SHA-256 checksums are published next to the download buttons so you can verify it first.
Can I undo a change Kytto made?
Yes. Every write checks whether the file changed outside Kytto, makes a timestamped backup, and then writes atomically. You can browse those backups inside the app and restore an earlier configuration — the version being replaced is backed up too.
Do I have to install my MCP servers through Kytto?
No. Kytto works with the servers you already configured and reads your existing configuration files as they are. You can add new servers manually or from the built-in catalog whenever you want, but nothing needs to be migrated first.
What does context cost mean?
Clients differ in how and when they load MCP tool definitions. Kytto estimates the full-schema footprint per server and profile as a consistent comparison, not exact per-conversation usage, and flags heavy definitions, unmeasured entries and duplicate tool names for review.
Does Kytto run on Linux?
Not yet. Beta 1.0.7.1 supports macOS and Windows, and the macOS build is universal, so it runs on both Apple Silicon and Intel Macs. Linux is not supported in this release.
An independent project
Built by Jakub Hecht.
KyttoMCP is made by Jakub Studio and is open source under the MIT License. Read the code, check the release history, report an issue, or get in touch with a question before you try it.
Help improve Kytto
Found a bug?
The private form goes straight to Jakub Studio. Prefer a public conversation? Open a GitHub issue instead.