Code Scanner Server MCP Server

Most developer tooling work still happens through a UI a human drives. Code Scanner Server MCP server moves it into the conversation instead. A CLI tool and MCP server that scans code files for definitions (classes, functions, etc.), respects .gitignore, provides line numbers, and outputs LLM-friendly formats (XML/Markdown).

The short version

This project provides a versatile code scanning tool built with TypeScript and Node.js. It leverages the Tree-sitter parsing library to analyze source code and extract structural information. It can operate both as a command-line interface (CLI) tool and as an MCP (Model Context Protocol) server.

• Code Definition Extraction: — Identifies functions, classes, variables, interfaces, methods, etc
• Multi-Language Support: — Parses JavaScript (.js, .jsx), TypeScript (.ts, .tsx), C# (.cs), PHP (.php), CSS (.css), and Python (.py) via Tree-sitter
• .gitignore Aware: — Automatically respects rules defined in .gitignore files
• Flexible Filtering: — Filter results by definition type, modifiers (public, private), name patterns (regex), and file path patterns
• Multiple Output Formats: — Generates results in Markdown (default), XML, or JSON
• Configurable Detail Levels: — Output verbosity: minimal, standard (default), detailed

Getting it running

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

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 Ixe1; 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.