Codeweaver MCP Server

Codeweaver MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Semantic code search built for AI agents. Hybrid, AST-aware, context for 166 languages.

What you get

What the assistant can call

Once Codeweaver is connected, these are the calls the assistant has available:

• AST — level understanding** (27 languages)
• Language — aware chunking** (166+ languages)
• Pydantic — driven validation** at boot-time
• Zero — code provider swapping**
• Privacy-First — ** Your code stays local if you want it to
• Feature — CodeWeaver
• Extensibility — DI-Driven (Zero-Code Provider Swap)
• Reliability — Resilient (Automatic Local Fallback)

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Codeweaver's toolset — AST, Language, Pydantic and 5 more — is a fair guide to whether it matches your workflow. It is maintained by com.knitli; 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.

Before you rely on it

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the codeweaver mcp server does with a few real requests.