Code Expert System MCP Server

If you already use Code Expert System, the code expert system mcp server is the piece that lets your assistant work with it directly. Simulate code reviews from expert personas using AI and a knowledge graph.

What the server does

A Python-based code review system using the Model Context Protocol (MCP). It provides code review capabilities through simulated expert personas like Martin Fowler and Robert C. Martin (Uncle Bob).

• Code review based on Martin Fowler's refactoring principles
• Code review based on Robert C. Martin's Clean Code principles
• Knowledge graph storage of code, reviews, and relationships
• Integration with Ollama for AI-powered reviews
• Server-side Event (SSE) support for web integration

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• ask_martin — Ask Martin Fowler to review code and suggest refactorings
• ask_bob — Ask Robert C. Martin (Uncle Bob) to review code based on Clean Code principles
• read_graph — Read the entire knowledge graph
• search_nodes — Search for nodes in the knowledge graph
• open_nodes — Open specific nodes by their names
• Ollama — Ollama is required for AI-powered code reviews

Installation

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

Credentials and setup notes

Configuration is passed through the environment: KNOWLEDGE_GRAPH_PATH, OLLAMA_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Code Expert System's toolset — ask_martin, ask_bob, read_graph and 3 more — is a fair guide to whether it matches your workflow. It is maintained by tomsiwik; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• 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.