English Français العربية

MCP AST Explorer

Registre officiel IA et agents

Python symbol exploration for codebase onboarding agents.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package mcp-ast-explorer
Claude Code 
claude mcp add mcp-ast-explorer -- uvx mcp-ast-explorer==0.1.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcp-ast-explorer": {
            "command": "uvx",
            "args": [
                "mcp-ast-explorer==0.1.0"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. mcp-ast-explorer
  2. Codebase Onboarding Stack
  3. Status
  4. Tools
  5. Supported Scope
  6. Current Limitations
  7. Local Development
  8. License

mcp-ast-explorer

MCP server for deterministic Python codebase symbol exploration.

mcp-ast-explorer indexes Python source files with LibCST and exposes focused MCP tools for codebase onboarding: definition lookup, function signatures, local references, direct call chains, and simple class hierarchy queries.

Codebase Onboarding Stack

mcp-ast-explorer is the semantic symbol layer in a three-server MCP tool stack for Project 6 wayfinder, a codebase onboarding agent.

  • mcp-repo-mapper maps repository structure, languages, entry points, framework evidence, and Python dependency edges.
  • mcp-ast-explorer provides symbol-grounded Python definition, signature, reference, call-chain, and class-hierarchy lookups.
  • mcp-test-runner runs local pytest/Jest checks and coverage summaries so agent claims can be verified against execution.

In wayfinder, this server feeds entry-point and symbol explanation while refusing to invent missing symbols.

Status

This is a Python-only v1. TypeScript is registered as an unsupported backend placeholder so the server has an explicit extension point, but TypeScript analysis is not implemented yet.

The server does not use an LLM for symbol lookup. If a requested symbol or class is not present in the parsed index, tools return a structured not-found result instead of inventing an answer.

Tools

ToolPurpose
health()Returns ok for smoke checks.
find_definition(path, symbol, language="python")Finds a module, class, function, or method definition.
function_signature(path, symbol, language="python")Returns the signature for a function or method symbol.
find_references(path, symbol, language="python")Returns same-module CST name references for an existing symbol.
call_chain(path, from_symbol, depth=2, language="python")Returns direct callers detected from local references.
class_hierarchy(path, class_name, language="python")Returns direct subclasses detected from simple base-class names.

Supported Scope

  • Python files parsed by LibCST.
  • Symbol kinds: modules, classes, functions, and methods.
  • Same-module reference lookup for simple names.
  • Direct caller detection from function or method containers.
  • Direct subclass detection for simple class Child(Base): inheritance.
  • Structured error responses for unsupported languages and missing symbols.

Current Limitations

  • Cross-file imports and package-wide resolution are out of scope for v1.
  • Aliases, star imports, dynamic attribute access, and qualified references are not resolved.
  • call_chain currently returns direct callers only; recursive multi-hop expansion is not implemented.
  • class_hierarchy currently returns direct subclasses only and handles simple base names.
  • TypeScript is intentionally unsupported in v1.

Local Development

Install dependencies:

uv sync --extra dev

Run the MCP server:

uv run mcp-ast-explorer

Run verification:

uv run ruff check .
uv run mypy
uv run pytest

License

MIT

Questions fréquentes

Qu'est-ce que MCP AST Explorer ?

Python symbol exploration for codebase onboarding agents.

Comment installer MCP AST Explorer ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add mcp-ast-explorer -- uvx mcp-ast-explorer==0.1.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour MCP AST Explorer ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

MCP AST Explorer est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient MCP AST Explorer ?

Il est publié par LovRanRan. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.