AiDex MCP Server

Persistent code indexing for AI assistants

README.md

AiDex

Stop wasting 80% of your AI's context window on code searches.

AiDex is an MCP server that gives AI coding assistants instant access to your entire codebase through a persistent, pre-built index. Works with any MCP-compatible AI assistant: Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI, VS Code Copilot, and more.

AiDex Demo - grep vs aidex

Animated version

AiDex Demo GIF

What's Inside — 30 Tools in One Server

Category Tools What it does
Search & Index init, query, update, remove, status Index your project, search identifiers by name (exact/contains/starts_with), time-based filtering
Signatures signature, signatures Get classes + methods of any file without reading it — single file or glob pattern
Project Overview summary, tree, describe, files Entry points, language breakdown, file tree with stats, file listing by type
Cross-Project link, unlink, links, scan Link dependencies, discover indexed projects
Global Search global_init, global_query, global_signatures, global_status, global_refresh Search across ALL your projects at once — "Have I ever written X?"
Guidelines global_guideline Persistent AI instructions & coding conventions — shared across all projects
Sessions session, note Track sessions, detect external changes, leave notes for next session (with searchable history)
Task Backlog task, tasks Built-in task management with priorities, tags, and auto-logged history
Log Hub log Universal log receiver — any program sends logs via HTTP, queryable by the AI, live in Viewer
Screenshots screenshot, windows Cross-platform screen capture with LLM optimization — scale + color reduction saves up to 95% tokens
Viewer viewer Interactive browser UI with file tree, signatures, tasks, logs, and live reload

11 languages — C#, TypeScript, JavaScript, Rust, Python, C, C++, Java, Go, PHP, Ruby

Quick Examples — see it in action
# Find where "PlayerHealth" is defined — 1 call, ~50 tokens
aidex_query({ term: "PlayerHealth" })
→ Engine.cs:45, Player.cs:23, UI.cs:156

# All methods in a file — without reading the whole file
aidex_signature({ file: "src/Engine.cs" })
→ class GameEngine { Update(), Render(), LoadScene(), ... }

# What changed in the last 2 hours?
aidex_query({ term: "render", modified_since: "2h" })

# Search across ALL your projects at once
aidex_global_query({ term: "TransparentWindow", mode: "contains" })
→ Found in: LibWebAppGpu (3 hits), DebugViewer (1 hit)

# Leave a note for your next session
aidex_note({ path: ".", note: "Test the parser fix after restart" })

# Create a task while working
aidex_task({ path: ".", action: "create", title: "Fix edge case in parser", priority: 1, tags: "bug" })

The Problem

Every time your AI assistant searches for code, it:

  • Greps through thousands of files → hundreds of results flood the context
  • Reads file after file to understand the structure → more context consumed
  • Forgets everything when the session ends → repeat from scratch

A single "Where is X defined?" question can eat 2,000+ tokens. Do that 10 times and you've burned half your context on navigation alone.

The Solution

Index once, query forever:

# Before: grep flooding your conte

Tools 5

querySearch identifiers by name or time-based filtering
signatureGet classes and methods of a file
taskManage project tasks with priorities and tags
noteLeave notes for future sessions
global_querySearch across all indexed projects

Try it

Find where the 'PlayerHealth' class is defined in my project.
List all methods available in src/Engine.cs without reading the whole file.
What code changes have been made in the last 2 hours?
Search across all my projects for 'TransparentWindow'.
Create a new task to fix the edge case in the parser with high priority.

Frequently Asked Questions

What are the key features of AiDex?

Persistent code indexing for instant AI access. Cross-project global search capabilities. LLM-optimized screen capture for token savings. Built-in task management and session note tracking. Interactive viewer with file tree and signature analysis.

What can I use AiDex for?

Reducing context window usage by avoiding full-file reads. Managing coding conventions across multiple projects. Tracking project progress and session-specific notes. Quickly locating definitions across large codebases. Centralizing logs from external programs for AI analysis.

How do I install AiDex?

Install AiDex by running: npx aidex-mcp

What MCP clients work with AiDex?

AiDex works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep AiDex docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Open Conare