Cntx Ui MCP Server

Most developer tooling work still happens through a UI a human drives. Cntx Ui MCP server moves it into the conversation instead. Autonomous Repository Intelligence engine with web UI and MCP server. Unified semantic code understanding, local RAG, and agent working memory.

The short version

Semantic code analysis and context management for AI agents. Turns a codebase into searchable, structured context that agents can navigate efficiently.

• Semantic analysis — — parses your code at the function level using tree-sitter, extracts purpose, complexity, and relationships
• Local vector search — — embeds code chunks locally (all-MiniLM-L6-v2 via Transformers.js) for semantic similarity search with no external API calls
• Bundle system — — group files into logical bundles (by feature, layer, or pattern) for structured context delivery
• MCP server — — exposes 28+ tools to Claude Code, Claude Desktop, or any MCP-compatible client
• Web dashboard — — visual interface at localhost:3333 for managing bundles, browsing semantic analysis, and editing agent rules
• Real-time sync — — watches for file changes and keeps analysis, bundles, and embeddings current

Getting it running

The server ships on npm as cntx-ui, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by nothingdao; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.