MCP Server for persistent code indexing. Gives AI assistants (Claude, Gemini, Copilot, Cursor) instant access to your codebase. 50x less context than
Aidex MCP server exists for a simple reason — assistants are far more useful when they can act on Aidex directly instead of describing what you should do. MCP Server for persistent code indexing. Gives AI assistants (Claude, Gemini, Copilot, Cursor) instant access to your codebase. 50x less context than grep.
AiDex is an MCP server that gives AI coding assistants a memory, semantic search, and live telemetry — local-first, model-agnostic. Works with any MCP-compatible AI assistant: Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI, VS Code Copilot, and more.
Once Aidex is connected, these are the calls the assistant has available:
Category — ToolsSignatures — signature, signaturesCross-Project — link, unlink, links, scanGuidelines — global_guidelineSessions — session, noteScreenshots — screenshot, windowsViewer — viewerOverview — aidex_summary, aidex_tree, aidex_describe, aidex_filesTasks — aidex_task, aidex_tasksaidex_init — Index a project (creates .aidex/)aidex_query — Search by term (exact/contains/starts_with)aidex_signature — Get one file's classes + methodsnode --version) - macOS: brew install node or nvm install 20 && nvm use 20 - Linux: use your package manager or nvm - Windows: nodejs.org - If you use nvm, the repo ships a .nvmrc — nvm use picks the right version automatically.aidex-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Aidex's toolset — Category, Signatures, Cross-Project and 11 more — is a fair guide to whether it matches your workflow. It is maintained by cscsoftware; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Category | Tools |
| Signatures | signature, signatures |
| Cross-Project | link, unlink, links, scan |
| Guidelines | global_guideline |
| Sessions | session, note |
| Screenshots | screenshot, windows |
| Viewer | viewer |
| Overview | aidex_summary, aidex_tree, aidex_describe, aidex_files |
| Tasks | aidex_task, aidex_tasks |
| aidex_init | Index a project (creates .aidex/) |
| aidex_query | Search by term (exact/contains/starts_with) |
| aidex_signature | Get one file's classes + methods |
| aidex_signatures | Get signatures for multiple files (glob) |
| aidex_update | Re-index a single changed file |
{
"mcpServers": {
"aidex": {
"command": "npx",
"args": ["-y", "aidex-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
node --version) - macOS: brew install node or nvm install 20 && nvm use 20 - Linux: use your package manager or nvm - Windows: nodejs.org - If you use nvm, the repo ships a .nvmrc — nvm use picks the right version automatically.Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.