Codebase intelligence MCP server — index any repo into a property graph; 24 tools for agents.
Codebase intelligence MCP server — index any repo into a property graph; 24 tools for agents. Exposed over MCP by the automatised mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Cross-platform codebase intelligence for Codex, Gemini CLI, Claude Code, Cursor, VS Code, Zed, and any stdio MCP host.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverDependencies — Deliberately not included: async runtime (we're stdio-blocking), HTTP client, LLM SDK, embedding model runtime (sparse TF-IDF replaces it at zeroStorage — Graphs are per-finding by design (Lamport's isolation invariant): each finding gets its own LadybugDB instance atrust-toolchain.toml, so rustup installs and selects it for you; the same compiler builds CI and the releases - CMake (LadybugDB builds its C++ core from source — ~5 minutes first build, cached after)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Automatised's toolset — Prerequisites, Dependencies, Storage — is a fair guide to whether it matches your workflow. It is maintained by cdeust; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Automatised's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Dependencies | Deliberately **not** included: async runtime (we're stdio-blocking), HTTP client, LLM SDK, embedding model runtime (sparse TF-IDF replaces it at zero dep cost). |
| Storage | Graphs are per-finding by design (Lamport's isolation invariant): each finding gets its own LadybugDB instance at <output_dir>/runs/<run_id>/findings/<finding_id>/graph/. Zero-coordination concurrency, trivial cleanup, n |
rust-toolchain.toml, so rustup installs and selects it for you; the same compiler builds CI and the releases - CMake (LadybugDB builds its C++ core from source — ~5 minutes first build, cached after)Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.