DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to connect any MCP client to the code graph with Axiomcodegraph

Add one config entry so an MCP-capable agent can query the graph.

Who it is forA developer using an MCP client that is not one of the named plugin agents and who wants the graph inside it.

The problemWithout a server entry, the graph built by the engine is only reachable from the shell, not from the agent handling the task.

The outcomeAn MCP client that starts the axiomcode server and can answer code questions from the same graph the CLI uses.

What you need first

  • Node.js 22.13 or newer
  • Python 3 (python3, or python or py on Windows)
  • Git for Windows on Windows, since the CLI runs under its bash
  • A supported AI agent or any MCP client, if you want agent use

Steps

  1. Install Node.js 22.13 or newer and Python 3.
  2. Add the entry below to your MCP client config file, using its server section:
  3. { "mcpServers": { "axiomcode": { "command": "npx", "args": ["-y", "@axiomcode/code-graph", "mcp"] } } }
  4. Start a new session in your MCP client so it loads the server.
  5. Ask the client a call-path question about one function in your project and check the result against axiomcode path <caller> <target> from the shell. (inferred, check the README)

Prompt for your agent

Using the axiomcode MCP server in <repo>, find the call path to <target> and list each hop with file and line. Expect the same hops that `axiomcode path` prints in the shell. Verify that both outputs match before reporting.

Caveat. The MCP server runs through npx, so the first start needs network access to fetch the package, and the README does not list the four MCP tool names beyond the ones shown in examples.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page