Table of Contents
- MCP Server: code-to-tree
- Using code-to-tree
- Configure MCP Clients
- Building (Windows)
- Building (macOS)
MCP Server: code-to-tree
The code-to-tree server's goals are:
- Give LLMs the capability of accurately converting source code into AST(Abstract Syntax Tree), regardless of language.
- One standalone binary should be everything the MCP client needs.
These goals imply:
- The underlying syntax parser should be versatile enough. Here we choose tree-sitter, and languages are: C, C++, Rust, Ruby, Go, Java, Python.
- The server should be able to carry all capabilities within itself, imposing minimum software dependencies on the end user's machine. Here we choose mcpc.
Screenshots:
The above screenshots are obtained by asking the question specified
in q.md.
(IMPORTANT NOTE: LLMs have no responsibility of generating the identical result for the same question, you will likely get a completely different style or content. The screenshots or questions provided here are just for the reference)
