Skip to content
Conduit

mcp server

kitden

See what your coding agents load. Change it with confidence.

KonstantinStarovoytov/kitdencommunitylistedunreviewed
Use tool

Set up

Runs on your computer. Pick your agent and operating system.

Before you start

  • uv (`curl -LsSf https://astral.sh/uv/install.sh | sh`)
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "kitden": {
      "command": "uvx",
      "args": [
        "kitden"
      ]
    }
  }
}

same format Cursor, GitHub Copilot CLI, Junie, JetBrains AI Assistant, Augment (Auggie CLI), Factory Droid, Kiro, Devin CLI +12

Values in angle brackets are placeholders. Restart Claude Desktop after editing its config.Claude Desktop docs

README

synced Oct 25, 2026

Everything your agents load, on one map

Claude Code, Codex and Cursor each keep their own settings. Kitden puts their plugins, skills, MCP servers and instruction files on one map, so what one agent has and another lacks shows at a glance. Add what an agent is missing, turn an item off or remove it, on the same page.

Find and add from one place

Search the official MCP Registry, skills.sh, the Claude plugins marketplace and any public GitHub repository without leaving the page. Tick the agents a plugin or skill goes to. An MCP server goes to the gateway, and says first whether it needs a sign-in or a token.

One gateway for your MCP servers

Move a server into the Kitden gateway and every agent you use gets it: set it up once, not once per agent. Every tool has a switch, for all projects or one, and a tool that is off is refused, not just hidden. A token or sign-in is given once and checked before Apply.

Every change can be undone

  • Nothing is written until you press Apply. Every change shows a preview first, with the exact edit under Show changes.
  • Apply keeps a backup, and Undo puts it back. Changes keeps the history of what you did. If a file changed since, Kitden stops instead of overwriting it.
  • Everything stays on your computer. The page runs at 127.0.0.1 behind a private link. No account, no telemetry. Kitden goes online only for the catalogs you open and the remote servers you add.
  • Secrets live in the macOS Keychain or your Linux keyring only. The page shows no more than their first and last characters.
  • Kitden's agent tools only read. Asking an agent to show your setup changes nothing.

Add only servers and plugins you trust: they run with your permissions.

And more

FeatureWhat it does
Per projectTurn a server or a tool on or off for one project only.
See what runsHow often each tool is called, and which tools only read.
Instructions in viewWhich CLAUDE.md, AGENTS.md, rules, hooks, commands and agents each client loads, and where they come from.
Ask your agent"Show my setup" works from any agent, through Kitden's own read-only MCP server.
Claude Code pluginWith Kitden installed, /plugin install kitden --marketplace KonstantinStarovoytov/kitden adds its skill and read-only tools to Claude Code. Codex has one too.

Get started

Needs macOS or Linux, uv and at least one of Claude Code, Codex or Cursor. On Linux, install libsecret-tools (Debian, Ubuntu) or libsecret (Fedora, Arch) so Kitden can keep server secrets in your keyring.

Try it on a sample first. Your own settings are not read or changed:

uvx --python 3.13 kitden demo

Install it and open it for your own setup:

uv tool install --python 3.13 kitden && kitden

Or with Homebrew: brew install konstantinstarovoytov/tap/kitden, then kitden.

Update later with uv tool upgrade kitden or brew upgrade kitden.

Guide · Roadmap · Releases · Issues · Contributing · Apache-2.0

↑↓ navigate openesc close