Loading ToolBench
MCP Server for persistent code indexing. Gives AI assistants (Claude, Gemini, Copilot, Cursor) instant access to your codebase. 50x less context than grep.
AiDex demonstrates strong definition quality with 28 well-structured tools covering code indexing, search, and project management. All tools have explicit schemas with proper type definitions and comprehensive parameter descriptions. Naming convention is consistent (aidex_* prefix) and descriptive. Most tools include actionable guidance for when to use them over alternatives. However, several tools lack explicit output schema documentation, and error handling guidance is minimal. A few tools (aidex_screenshot, aidex_listWindows) perform actions tangential to the core code indexing mission, introducing slight composition concerns. Tool descriptions average ~180 chars and generally exceed the 10-1024 char guideline. Parameter descriptions are detailed and context-aware. The server demonstrates strong adherence to patterns:tool and pattern:tool-description through consistent, LLM-optimized descriptions.
Get full description of a file including all method bodies and comments. Use sparingly — only when you need the complete implementation. For signatures only, use aidex_signature instead.
List all indexed files in a project with file size and last-modified timestamp.
Set or get global guidelines for AI behavior. Guidelines are persisted and applied to all cross-project searches.
Scan a directory tree for all projects and register them in the global index (~/.aidex/global.db). Optionally index unindexed projects. Enables cross-project search.
Search across ALL registered projects in the global index. Same search options as aidex_query but returns results from all projects.
Scan for new projects or removed projects and update the global index. Re-indexes existing projects if their source files have changed.
Get signatures across ALL registered projects. Same as aidex_signatures but searches all indexed projects in the global index.
Output schemas not documented for ANY tool. LLMs cannot predict result structure or plan downstream tool calls.
No error handling guidance. Tools do not explain what errors can occur, whether they're retryable, or what the LLM should do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | D | 59 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 46 | - | v1 |
Get status of the global index: list of all registered projects, statistics, and sync status.
Initialize AiDex indexing for a project. Scans all source files and builds a searchable index of identifiers, methods, types, and signatures.
Link two projects together for cross-project search and signatures. Both projects must already be indexed.
List all projects linked to the given project.
List all open windows on the system with titles and bounds. Useful for identifying which window to capture with aidex_screenshot.
Write structured log entries (with automatic timestamp) and access the persistent log store. Supports debug, info, warn, error levels.
Read or write a project session note. Session notes are markdown files attached to a project for storing context, plans, and observations during a work session.
Search for terms/identifiers in the AiDex index. Returns file locations where the term appears. PREFERRED over Grep/Glob for code searches when .aidex/ exists - faster and more precise. Use this instead of grep for finding functions, classes, variables by name.
Remove a file from the AiDex index. Use when a file has been deleted from the project.
Scan a directory tree for existing .aidex indexes. Returns a list of indexed projects found.
Capture a screenshot of the active monitor or a specific window. Returns base64-encoded PNG image.
Get session info: current work-in-progress changes. Tracks files modified or created since the last session checkpoint.
Get the signature of a single file: header comments, types (classes/structs/interfaces), and method prototypes. Use this INSTEAD of reading entire files when you only need to know what methods/classes exist. Much faster than Read tool for understanding file structure.
Get signatures for multiple files at once using glob pattern or file list. Returns types and method prototypes. Use INSTEAD of reading multiple files when exploring codebase structure. Much more efficient than multiple Read calls.
Get AiDex server status and statistics for an indexed project
Get project summary including auto-detected entry points, main types, and languages. Also returns content from summary.md if it exists.
Create, update, close, or delete a task. Tasks are persistent work items stored per-project for tracking TODOs, bugs, refactoring, and other action items.
List all tasks in a project, optionally filtered by status. Tasks track TODOs, bugs, refactoring work, and action items.
Get project file tree (code files only). Useful for understanding project structure before making changes.
Unlink two projects. After unlinking, cross-project searches will no longer include the target project.
Re-index a single file. Use after editing a file to update the AiDex index. If the file is new, it will be added to the index. If unchanged (same hash), no update is performed.
Composition: aidex_screenshot and aidex_listWindows are tangential to the core code indexing mission. They feel like feature creep and reduce tool focus.
No pagination or result limits documented for list/search tools. Large result sets may overflow context windows.
Naming of aidex_remove and aidex_log are somewhat generic. LLMs may conflate aidex_remove with filesystem deletion; aidex_log with logging system (which is deprecated).