Dev Agent is a repository-aware context provider that helps AI tools like Claude Code understand codebases more deeply without having to process the entire repository. By providing relevant context, Dev-Agent reduces hallucinations, improves the accuracy of AI responses, and optimizes token usage.

dev-agent

Local semantic code search for Cursor and Claude Code via MCP.

What it does

dev-agent indexes your codebase and provides 9 MCP tools to AI assistants. Instead of AI tools grepping through files, they can ask conceptual questions like "where do we handle authentication?"

• dev_search — Semantic code search by meaning
• dev_refs — Find callers/callees of functions
• dev_map — Codebase structure with change frequency
• dev_history — Semantic search over git commits
• dev_plan — Assemble context for GitHub issues
• dev_inspect — Inspect files (compare similar code, check patterns)
• dev_gh — Search GitHub issues/PRs semantically
• dev_status / dev_health — Monitoring

Measured results

We benchmarked dev-agent against baseline Claude Code across 5 task types:

Trade-offs: Faster but sometimes less thorough. Best for implementation tasks and codebase exploration. For deep debugging, baseline Cursor may read more files.

When to use it

Good fit:

• Large or unfamiliar codebases
• Implementation tasks ("add a feature like X")
• Exploring how code works
• Reducing AI API costs

Less useful:

• Small codebases you already know well
• Deep debugging sessions
• When thoroughness matters more than speed

Quick Start

# Install globally
npm install -g dev-agent

# Index your repository (initial indexing can take 5-10 minutes for large codebases)
cd /path/to/your/repo
dev index .

# Install MCP integration
dev mcp install --cursor  # For Cursor IDE
dev m