A local control panel for MCP servers across the AI clients you already use.
Free and open source under the MIT License — the full source of both the macOS and the Windows app lives in this repository. Read it, build it, or send a pull request.
Download the beta · Website · Source code · Contributing · Changelog · Report a bug
A test server passes its health check. One command changes the description of its only tool, with the same server version and the same input schema, and the next health check shows the old and the new text side by side. Contract Guard flags the change for review; it does not block the server or edit a config. drift-fixture is a harmless server written for this demonstration, and the instruction in its description is a sample that does nothing. Recorded on Windows with Beta 1.0.9.3 and trimmed from a 59-second take with hard cuts only; one line of the matrix is covered because it showed a local path. What else Kytto reads in a tool definition.
kytto-demo.mp4
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.
Once you run more than two or three MCP servers, the configuration is spread across files that share nothing but the idea:
| Client | macOS | Windows |
|---|---|---|
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json |
%APPDATA%\Claude\claude_desktop_config.json |
| Claude Code | ~/.claude.json (servers); ~/.claude/settings.json (deniedMcpServers) |
%USERPROFILE%\.claude.json (servers); %USERPROFILE%\.claude\settings.json (deniedMcpServers) |
| Cursor | ~/.cursor/mcp.json |
%USERPROFILE%\.cursor\mcp.json |
| VS Code | ~/Library/Application Support/Code/User/mcp.json |
%APPDATA%\Code\User\mcp.json |
| Codex | ~/.codex/config.toml |
%USERPROFILE%\.codex\config.toml |
| Antigravity | ~/.gemini/config/mcp_config.json |
%USERPROFILE%\.gemini\config\mcp_config.json |
| Devin Desktop (formerly Windsurf) | ~/.config/devin/mcp_config.json |
%APPDATA%\devin\mcp_config.json |
| OpenCode | ~/.config/opencode/opencode.json (mcp) |
%USERPROFILE%\.config\opencode\opencode.json (mcp) |
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?
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 touching the others — Kytto writes each client in that client's own format and respects its rules. Add servers by hand or from a built-in catalog. Since 1.0.5, Kytto explains the first matrix write before it happens and offers Undo after successful changes, including exact backup restoration for a server that was previously absent. Most clients only read their configuration at launch, so Kytto says which ones still need a restart — and since 1.0.9.3 it can restart Claude Desktop, Cursor, VS Code, Antigravity and Devin Desktop for you, after asking, because unsaved work in them may be lost.
Handle secrets without surprises 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 tighten config file permissions.
Attach custom sources without writing them Attach multiple named JSON, JSONC or TOML configuration files as read-only custom sources with Global, Profile or Workspace display scope. Kytto discovers and watches their servers without rewriting, creating or deleting the selected files, and keeps them distinct from the built-in writable clients.
Find out why a server fails
Run an on-demand MCP handshake and read what the server actually reports: tools, prompts, resources, protocol details and stderr. MCP Doctor turns that evidence into concrete findings — missing environment values, relative paths, failed handshakes, executables that only resolve inside one client's PATH — and previews any fix before writing it. A package a server fetches by name without an exact version (npx some-package, @latest, uvx) is flagged, and once you check the latest release Doctor can pin that exact version in every client that uses it. Package names that imitate an official server (mcp-server-github) and archived reference servers that get no more fixes (@modelcontextprotocol/server-github, -puppeteer, -slack and others) are flagged offline; "Check package safety" asks osv.dev about known malware and vulnerabilities and the npm registry about install scripts and deprecation, only when you click.
Read what a server tells your model
A tool's name, description and input schema go straight into the model's context, so an MCP server can give instructions without ever being called. The Tool Safety Scanner reads them the way the model does and reports what a person would not see: hidden or direction-override characters, wording that addresses the model instead of describing the tool ("ignore previous instructions"), markup that imitates a system message, a tool advertised as read-only that names credential files, and two enabled servers claiming the same tool name in one client, and wording that tells the model not to ask you ("skip confirmation"). Contract Guard remembers each server's tool contract between health checks and reports tools that were added or removed and changed descriptions, input schemas or safety annotations. Since 1.0.9.5 every change carries two labels: whether existing calls still fit (Compatible, Breaking or Compatibility unknown) and whether it is worth reading for security, each with its reason — a new optional argument is not breaking, and a new filePath argument is still worth a look. Acknowledge a change and the contract you reviewed becomes the new baseline.
Both are advice. Nothing is switched off and no config is edited, the scan is deliberately narrow so a finding is worth reading, and a clean scan does not mean a server is trustworthy. Version 1.0.7.1 fixed reordered schema keys (#12) and detection of bidi isolate characters (#13). Source: macOS · Windows.
Kytto 1.0.7 on Windows after two health checks of a test server whose description changed between them. drift-fixture is a harmless server written for this demonstration; the instruction in its description is a sample and does nothing.
Compare tool-schema footprint Clients differ in how and when they load MCP tool definitions. Kytto estimates the full-schema footprint of each server and profile as a consistent comparison, not exact per-conversation usage, and flags heavy definitions, unmeasured entries and duplicate tool names for review. For clients with a known tool limit — VS Code refuses a chat request with more than 128 tools — Kytto shows how many tools the servers switched on there offer against that limit and warns when you are near or over it. Claude Code and Codex defer MCP tools behind tool search, so for them Kytto also shows what the tool names alone cost before a search; for other clients it says it has not verified how they load tools.
Switch between setups Save local profiles such as Coding, Research or Minimal. Preview exactly what a switch will change, then apply it to one client with the normal backup and restart safeguards.
Undo anything Every write checks whether the file changed outside Kytto, makes a timestamped backup, and writes atomically. Browse those backups in the app and restore an earlier configuration — the version being replaced is 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. Live Activity shows sessions, tool calls, latency and failures as metadata only — arguments, results and payloads stay out of the log. Since 1.0.9.4, a Gateway server that fails says why: MCP Doctor names a missing helper, a lost route, an unreadable secret or a server that keeps stopping, repairs the route when Kytto was moved, and can restore Direct mode for everything before you remove Kytto.
| Client | Status |
|---|---|
| Claude Desktop | Supported |
| Claude Code | Supported |
| Cursor | Supported |
| VS Code | Supported |
| Codex | Supported |
| Antigravity | Supported |
| Devin Desktop (formerly Windsurf) | Supported |
| OpenCode | Supported |
Custom sources are read-only and are not an additional writable client. Project folders (since 1.0.9.5) show the MCP files a repository commits — .mcp.json, .cursor/mcp.json, .vscode/mcp.json — in folders you choose, read-only; a server found only there is never checked unless you ask, because a check starts it. Want another built-in client supported? Open an issue — the roadmap is driven by what people actually ask for.
Download from kytto.jakubhecht.sk or from GitHub Releases: Beta 1.0.9.5 for macOS (v1.0.9.5) and Beta 1.0.9.5 for Windows (v1.0.9.5-windows).
Universal build — runs on both Apple Silicon and Intel Macs. Open the DMG and drag KyttoMCP into Applications.
The beta is not signed with a paid Apple Developer certificate, so Gatekeeper will show an "unidentified developer" warning. Control-click the app and choose Open, then Open again. If macOS still blocks it, go to System Settings → Privacy & Security → Open Anyway.
Kytto is distributed unsigned: there is no paid Apple Developer or Windows signing certificate, and none is planned for now (#4). The code is open instead. Only open a build you downloaded from the official site or this repository's Releases page and verify the checksum below — or build it yourself from source, which needs no warning bypass at all.
Run the setup file. Microsoft Defender SmartScreen will appear for the same reason — choose More info → Run anyway.
# macOS
shasum -a 256 KyttoMCP-1.0.9.5.dmg
# 45f2481c3a5a1954940f3a475d06e7fe72b37159684fb2b838fdc144078dd0c2
# Windows (PowerShell)
Get-FileHash Kytto-Setup-win-x64-1.0.9.5.exe -Algorithm SHA256
# 1e5e02713547d0eccd4cbe05188fbb621d487edee5df95f955f0725e2123711dKytto works with the files already on your computer.
- No account, no sign-up, no cloud sync
- MCP configurations and credentials never leave your machine
- Backups and configuration changes are handled locally
- No telemetry or analytics. The only request the app makes on its own is the update check; a package version lookup and a package safety check (osv.dev, and the npm registry for npm packages) happen only when you ask for them. The platform READMEs list every request. (Builds up to 1.0.6.3 included opt-in anonymous diagnostics, off by default; the source here has removed them.)
- Gateway activity is metadata-only; payload capture is off
See the privacy policy for details.
Kytto is free and open source under the MIT License. This repository holds both apps:
| Folder | Platform | Stack | Start here |
|---|---|---|---|
macos/ |
macOS 15+ | Swift 6, SwiftUI/AppKit shell, WKWebView | macos/README.md |
windows/ |
Windows 10/11 | .NET 10, WPF shell, WebView2 | windows/README.md |
Both are a native shell around a web UI (vanilla HTML/CSS/JS, no build step), talking over a typed IPC contract, and both follow the same design document: macos/README.md (§1–§12) and windows/docs/design.md. Each folder builds and tests on its own:
git clone https://github.com/heyitsjakub/KyttoMCP.git
# macOS (Xcode 16+)
cd KyttoMCP/macos/KyttoCore && swift test
# Windows (.NET 10 SDK)
cd KyttoMCP/windows && dotnet testBoth apps load the same UI from web/; the few places where the two
native backends answer a command differently are translated in one file,
web/js/compat.js.
The Xcode project names the maintainer's signing team, so a plain xcodebuild
asks for a certificate you do not have. The release script builds the same
universal app ad-hoc signed, with no account and no team, and refuses to produce
a DMG unless the result passes its own checks (universal binary, valid ad-hoc
signature, no get-task-allow entitlement, no provisioning profile, the app
launches and keeps running):
cd KyttoMCP/macos
scripts/make-dmg.sh # Xcode 16+; writes dist/KyttoMCP-<version>.dmgA build made on your own machine carries no quarantine flag, so Gatekeeper shows no warning. Its SHA-256 will not match the published one (builds are not bit-for-bit reproducible), so the checksums in Verify your download are for the files on the Releases page, not for your own build.
Issues and pull requests are welcome — start with CONTRIBUTING.md. Writing to someone else's config file is
the whole risk of this app, so every write goes through one pipeline — digest
check, backup, span-level edit that preserves comments and key order, atomic
write — and parser or writer changes need round-trip tests. The platform READMEs
and their CLAUDE.md / AGENTS.md files carry the house rules.
- Not an MCP server and not a server registry. It manages the client-side configuration of servers you already run.
- Not a cloud service. There is nothing to sign into.
- Not a replacement for your client. It configures Claude Desktop, Cursor and the rest — it does not replace them.
Tracked in Issues. Priorities come from what people ask for, so an issue with a real use case in it carries more weight than a vote.
The beta needs honest criticism far more than it needs praise. If something is confusing, broken, or simply not worth keeping, that is the useful report.
MIT — see LICENSE. Bundled third-party components are listed in macos/THIRD_PARTY_NOTICES.md and windows/THIRD-PARTY-NOTICES.md.
Made by Jakub Hecht · Jakub Studio
Not affiliated with Anthropic, Cursor, Microsoft or OpenAI. Claude, Cursor, VS Code and Codex are trademarks of their respective owners.




