Everything you need to manage MCP.
Encrypted Vault
AES-256-GCM encryption with Argon2id key derivation. All credentials, configs, and keys stay on your machine — never in the cloud.
Multi-Assistant
Manage MCP configs for Claude Code, Gemini CLI, ChatGPT, and Codex from one interface. Per-project, per-model config files synced to disk.
SSH Tunnels
Create, start, stop, and monitor SSH tunnels to reach remote MCP servers behind firewalls. Password and private key auth both supported.
MCP Marketplace
Browse community-verified MCP servers and install them with one-click wizards. Auto-configures credentials and SSH tunnels for remote databases.
Environment Profiles
Separate MCP server configs per environment — Default, Development, Staging, and Production. Your local dev database never touches production.
Built-in MCP Server
A localhost HTTP server lets AI agents manage projects, add servers, and control tunnels programmatically via tool calls — secured with a bearer token.
Connection Testing
Test any server config before deploying it. Checks TCP reachability and MCP server process spawn health, with latency shown inline on each card.
Encrypted Backups
Export your entire vault — projects, credentials, tunnels, SSH keys — as an encrypted backup file with a separate password. Import to merge into any vault.
Auto-Lock
Configurable inactivity timeout locks the vault and closes all SSH tunnels. While locked, the MCP server returns 503 and no credentials remain in memory.
Import Existing Configs
Paste your existing ~/.claude.json into the import dialog and Kodex automatically detects all projects and MCP servers and loads them into the vault.
Debug Log
Real-time structured log viewer with level filtering (debug, info, warn, error). Logs rotate on disk with 14-day retention for diagnosing connection failures.
System Tray
Minimizes to the system tray instead of closing. Tray menu shows live tunnel status, a quick lock action, and show/quit — active tunnel count updates every 15 seconds.
Production-grade security for multi-agent systems.
The built-in MCP server doubles as an enterprise gateway — proxying multiple downstream servers, protecting against supply-chain attacks, and issuing scoped credentials.
Tool Multiplexing
Register multiple downstream MCP servers and expose all their tools through a single gateway endpoint. Each server's tools are namespaced (db__query_rows) to prevent collisions and avoid God-Mode context degradation in agents.
Rug-Pull Detection
Trust-on-first-use fingerprinting detects when a downstream MCP server silently modifies its tool definitions. Changed tool schemas are blocked with HTTP 409 until you explicitly consent to the update — protecting against supply-chain attacks.
Scoped Token Exchange
Issue short-lived tokens restricted to a named subset of tools (RFC 8693). A scoped token expires in minutes and can only call the tools you allowed — limiting blast radius if a token is ever compromised.
Stateless Protocol (SEP-1442)
Serverless functions and CI runners get the tool result and its full JSON Schema in a single round trip — no separate schema discovery step. Enables ephemeral clients that can't maintain session state.
Cut AI spend automatically.
A layered set of caches and filters between your agents and their tools — fewer redundant calls, smaller payloads, and lower API bills with zero code changes.
Adaptive Output Pruning
Tool output is automatically trimmed based on the agent's remaining context budget (via the x-mcp-context-budget header). Truncated responses include a summary so the agent knows data was omitted.
Session Deduplication Cache
Identical read-only tool calls within a session are served from an in-memory cache for 60 seconds. Mutating tools always execute. Deduped responses carry x-mcp-deduped: 1 so agents can detect cache hits.
Prompt Caching
The /context endpoint returns Anthropic-compatible prompt-caching blocks (system instructions, CLAUDE.md, blueprint, symbol map) — enabling up to 90% token cost reduction on repeated Claude API requests.
Semantic Query Cache
Knowledge-base lookups use a two-level cache with 7-day TTL: exact SHA-256 match first, then trigram fuzzy match at ≥ 85% similarity. Eliminates redundant AI API calls for similar codebase questions.
Tool Filtering
Code Mode exposes only two meta-tools (portal_search / portal_execute), hiding management overhead from coding agents. Scoped tokens restrict discovery to permitted tools only.
Rate Limiting & Health Cache
60 requests per minute per IP prevents runaway agent loops. Downstream server health is cached (healthy: 5 min, unhealthy: 30 s) so repeated timeouts don't burn agent context on unreachable servers.
Stop wasting 40–70% of your context window.
Most AI coding agents burn their context on CLAUDE.md dumps, verbose tool responses, and stale history before writing a single line of code. Kodex ships a 7-feature compression engine — all rule-based, zero latency, no secondary model.
Tiered Context Injection
Agents request only the layers they need — /context?layers=knowledge,blueprint — skipping static boilerplate entirely. No more sending the full system prompt when all the agent needs is the symbol map.
Sidecar Compressed Docs
CLAUDE.md is compressed at project-creation time using structural regex, cutting the largest context block by 40–60% before the first request is ever made. The unmodified original is preserved on disk.
Frequency-Ranked Symbol Map
TF-IDF scoring surfaces your most-called functions first in the knowledge block. When the 4,000-char cap kicks in, it cuts low-value symbols — not the ones your agents actually use.
Boilerplate Stripper
GitHub admonition blocks, HTML comments, and badge images are stripped server-side on request. Agents receive clean, signal-only documentation without any markup noise.
Async Tool Output Compression
JSON results are structurally compressed in a background thread — null fields dropped, homogeneous arrays collapsed — before being returned to the agent. First-call latency is zero; the compression happens out of band.
Milestone Checkpoint Blocks
Jules workflow state (waiting, PR opened, CI pass, merged) is persisted to .claude/checkpoints.json and surfaced as a single 100-token block — replacing the multiple tool calls that would otherwise reconstruct the same state.
Conversation Distillation
POST /context/distill extracts headings, decisions, and code summaries from a full conversation history — compressing 10,000 tokens to under 1,000 while preserving every actionable decision.
Combined: 40–70% context reduction on typical agentic workflows.
More tokens for the work that matters.
From prompt to merged PR — hands free.
Kodex ships a complete three-agent pipeline. One prompt, and the Orchestrator, Researcher, and Implementer handle the rest — including branch creation, code, CI, security review, and auto-merge.
Orchestrator — Claude Code
Decomposes tasks, writes GitHub Issues with detailed specs, applies the jules label to trigger the Implementer, reviews PRs, and merges when CI passes.
Researcher — Gemini CLI
Read-only codebase analysis and internet research using Gemini's 1M+ token context window. Preserves the Orchestrator's token budget by handling all exploratory reads.
Implementer — Jules
Async cloud implementation: creates branches, writes code, opens PRs, and self-heals CI failures — all without blocking your local machine. Watched by Kodex's Sentinel until the PR merges.
Triage Hook
A pre-edit hook intercepts every JS/TS file change and routes it by size — small edits bypass to Claude, medium edits optionally delegate, large edits enforce full triage. No oversized changes land without review.
Watch Sentinel
Armed automatically when a Jules issue is created, the Sentinel polls for the Implementer's PR, waits for CI, runs a security review, and auto-merges — no human follow-up required for routine changes.
Agent Monitor & Quotas
Tracks per-agent invocation counts across rolling windows (Claude: 5-hour / 7-day, Jules: 24-hour). Opt-in enforcement returns HTTP 429 when limits are hit. Includes a live Jules task dashboard synced against GitHub.
Auto-Deploy to New Projects
Adding a project through Kodex's onboarding wizard automatically scaffolds the full workflow: triage hook, sentinel arming, CLAUDE.md, AGENTS.md, blueprint, and CLI reference — ready on first use of Claude Code.
Built for teams that delegate work to AI agents.
If you're using Claude Code, Gemini CLI, and Google Jules together, you've probably hit the same coordination problems: PRs that get lost in queues, feedback that gets ignored, status checks that fail silently, and new features that never reach your existing projects. Kodex ships a complete coordination layer that handles all of this for you.
Auto-Deployed Workflow Scaffolds
Every project gets the same playbook, automatically. When you add a project to Kodex, the app silently drops a complete set of coordination files into the project directory. Triage hooks, monitor scripts, agent rules — all in place before you write your first prompt.
Update All Projects
One click. Every project. Latest features. Upgraded Kodex and want your existing projects to pick up the new coordination scaffolds? Click one button in Settings and watch the per-project, per-feature status table fill in. Idempotent — safe to run repeatedly.
Robust Jules PR Monitor
Never miss a Jules update. Four independent detection methods. The deployed monitor watches a Jules-labeled issue from creation through merge, using four parallel detection paths — Jules CLI session status, comment-keyword scan, PR search, and comment link extraction — so a failure in any one doesn't go silent.
PR Review Comment Feedback Loop
Talk to Jules the way Jules listens. Jules only responds to PR review comments with an @jules mention — not the plain comments most tools default to. Kodex's monitor uses a three-tier fallback chain (request-changes → review comment → re-label) to ensure every message gets through.
/loop Continuous Monitoring
Set Claude Code on autopilot for batch PR work. When you have 3+ Jules PRs in flight, /loop runs the orchestrator on a 15-minute interval — reviewing, merging, and requesting fixes without you having to ask. Bound by four hard rules that prevent silent bad merges.
Tightened Merge Policy
No script auto-merges. Every PR gets human-grade code review. Kodex's monitor flags merge-ready PRs but never pulls the trigger itself — the orchestrator reads every changed file first. Sensitive files require human approval in addition to orchestrator review.
One manifest. Every project. Forever.
Every feature above is driven by a single registered manifest. When new coordination tools ship, they're added to the manifest — and every existing project picks them up the next time you click Update All Projects. You don't have to think about it.
Platform Support
Free to start. Upgrade for sync and commercial use.
All the tools you need to manage MCP configurations. No credit card required to get started.