MCP Catalogs
Home

codeTree

by ThinkyMiner·25·Score 46

MCP server with 23 tools for structured code understanding via tree-sitter across 10 languages.

developer-toolsai-llmknowledge-graph
6
Forks
1
Open issues
1 mo ago
Last commit
2d ago
Indexed

Overview

codeTree is an MCP server that provides AI coding agents with structured code understanding through tree-sitter parsing. It offers 23 tools for code analysis including skeleton extraction, symbol resolution, call graph generation, complexity analysis, dead code detection, and change impact analysis. The server supports 10 popular programming languages including Python, JavaScript, TypeScript, Go, Rust, Java, C, C++, and Ruby, with a one-command installation process via uv.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Code analysis and refactoring assistance
you:Documentation generation suggestions
you:Impact analysis before making code changes
you:What makes codeTree different from reading files directly?
you:Does codeTree replace LSP servers?

When to choose this

Choose codeTree when you need efficient code analysis for AI agents working across multiple languages without the overhead of vector databases or complex configuration.

When NOT to choose this

Don't choose codeTree if you need real-time code modification capabilities or are working with languages not in its 10-language support list.

Tools this server exposes

12 tools extracted from the README
  • get_file_skeletonget_file_skeleton(file_path)

    Get classes, functions, methods with line numbers + doc comments

  • get_symbolget_symbol(file_path, symbol_name)

    Get full source of a function or class

  • find_referencesfind_references(symbol_name)

    Find all usages of a symbol across the repository

  • get_call_graphget_call_graph(file_path, function_name)

    Get what a function calls and what calls it

  • get_complexityget_complexity(file_path, function_name)

    Get cyclomatic complexity breakdown

  • search_symbolssearch_symbols(query?, type?, parent?)

    Flexible symbol search with filters

  • get_repository_mapget_repository_map(max_items?)

    Get compact repo overview: languages, entry points, hotspots

  • get_change_impactget_change_impact(symbol_query?, diff_scope?)

    Analyze impact of code changes with risk levels

  • analyze_dataflowanalyze_dataflow(file_path, function_name, mode?)

    Analyze variable dataflow or taint tracing

  • get_dependency_graphget_dependency_graph(file_path?, format?)

    Get file-level dependency graph as Mermaid or list

  • find_testsfind_tests(file_path, symbol_name)

    Find test functions for a specific symbol

  • suggest_docssuggest_docs(file_path?, symbol_name?)

    Find undocumented functions with context for doc generation

Comparable tools

semantic-mcpast-mcptree-sitter-lspcode-analyzer-mcp

Installation

Installation

**Prerequisite:** Install [uv](https://docs.astral.sh/uv/getting-started/installation/) if you don't have it (curl -LsSf https://astral.sh/uv/install.sh | sh).

Then cd into any project and run:

claude mcp add codetree -- uvx --from mcp-server-codetree codetree --root .

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "codetree": {
      "command": "uvx",
      "args": ["--from", "mcp-server-codetree", "codetree", "--root", "/path/to/your/project"]
    }
  }
}

FAQ

What makes codeTree different from reading files directly?
codeTree reduces token consumption by up to 25x by providing structured code understanding without reading entire files. Agents can ask for specific symbols, skeletons, or relationships rather than processing raw code.
Does codeTree replace LSP servers?
No, codeTree complements LSP servers by providing a lightweight, language-agnostic approach to code understanding through MCP. It's designed specifically for AI agents rather than human developers.

Compare codeTree with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.