Get
Started
Install, configure, and run your first analysis in under five minutes.
Clone and Build
Clone the repository and build the MCP server locally. Conducks runs as a local process, no cloud, no account.
$ git clone https://github.com/conducks/conducks $ cd conducks $ npm run bootstrap && npm run build
Configure MCP Client
Add the following to your MCP host config (Claude Desktop, Cursor, or any MCP-compatible client):
{
"mcpServers": {
"conducks": {
"command": "node",
"args": ["/absolute/path/to/conducks/build/src/interfaces/cli/index.js", "mcp"]
}
}
}Use the absolute path. The MCP protocol requires it to anchor the server correctly to your filesystem.
Run your first analysis
Navigate to any project and run the analysis. Conducks builds the graph, scores it, and persists everything to a local DuckDB vault under .conducks/.
$ cd your-project $ conducks analyze # builds the structural graph into .conducks/ $ conducks status # hotspots, entry points, god objects, staleness $ conducks mirror # real-time force-directed graph at localhost:3333
13 MCP Tools
All agent interactions go through these tools. Tool descriptions load live, so updating your docs updates what the agent understands without a server restart.
CLI Reference
33 commands across 9 domains. Run conducks help for the full reference, grouped by domain.
