aptu-coder
MCP code-intelligence server that gives agents symbol tables and call graphs via tree-sitter.
Tested on macOS and Linux
Use it
macOS arm64
brew install clouatre-labs/tap/aptu-coder
brew install clouatre-labs/tap/aptu-coder
Check that it works
aptu-coder --versionThe output should contain “aptu-coder 0.41.1”.
Add it to your agent
claude mcp add aptu-coder -- aptu-coderJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"aptu-coder": {
"command": "aptu-coder",
"args": []
}
}
}Add aptu-coder as an MCP server command in your MCP client, then ask the agent to use its tools such as analyze_directory.
Linux x86_64
Install binary to ~/.local/bin
mkdir -p ~/.local/bin && curl -fsSL -o /tmp/aptu2.tar.gz https://github.com/clouatre-labs/aptu-coder/releases/download/v0.41.1/aptu-coder-0.41.1-x86_64-unknown-linux-musl.tar.gz && tar -xzf /tmp/aptu2.tar.gz -C /tmp && cp /tmp/aptu-coder ~/.local/bin/aptu-coder && chmod +x ~/.local/bin/aptu-coder
Check that it works
cp /tmp/aptu-coder ~/.local/bin/aptu-coder && chmod +x ~/.local/bin/aptu-coder && aptu-coder --versionThe output should contain “aptu-coder 0.41.1”.
Add it to your agent
claude mcp add aptu-coder -- aptu-coderJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"aptu-coder": {
"command": "aptu-coder",
"args": []
}
}
}Add aptu-coder as an MCP server command in your MCP client, then ask the agent to use its tools such as analyze_directory.
What it does
- Map a directory tree with symbol countsTested
How to use it
- In your MCP client, call the
analyze_directorytool. - Set
pathto <your project folder>.
- In your MCP client, call the
- List the functions, classes and imports in a fileTested
How to use it
- In your MCP client, call the
analyze_filetool. - Set
pathto <your source file>.
- In your MCP client, call the
- Trace the call graph for a named symbolTested
How to use it
- In your MCP client, call the
analyze_symboltool. - Set
pathto <your project folder> andsymbolto <symbol name>.
- In your MCP client, call the
How far pickfit got
macOS arm64
- Installs
- Connects
- 3 of 3 features work
- Works offline
Linux x86_64
- Installs
- Connects
- 3 of 3 features work
- Works offline
Other systems
Good for
- map directory structure of a codebase
- extract symbols from source files
- trace call graphs for a named symbol
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
macOS arm64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 1 Nov 2026
- Version 0.41.1
An MCP client handshake over stdio listed 8 tools, and a call to analyze_directory returned a result.
Differences the test machine hit
- README: README shows tools take a `path` without mentioning sandboxing
In the test: path must be inside the server's working directory; passing /tmp/mcp_test_proj returns 'path is outside the working directory' and suggests providing a path within the current working directory
Linux x86_64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 0.41.1
An MCP client handshake over stdio listed 8 tools, and a call to analyze_directory returned a result.
Differences the test machine hit
- README: cargo binstall aptu-coder / cargo install aptu-coder
In the test: downloaded x86_64-unknown-linux-musl tarball from GitHub releases v0.41.1 and copied aptu-coder to ~/.local/bin; both ranked cargo candidates need a Rust toolchain which the box does not have and must not install - README: tools take a path argument
In the test: run probe from the analyzed directory (cd /tmp/sampleproj) and pass relative paths ('.', 'demo.py'); absolute paths outside cwd fail with 'path is outside the working directory'