Welcome to ACECode

ACECode indexes your code once and serves it back through the Model Context Protocol to Claude, Cursor, VS Code, or any MCP-compatible AI — with semantic search, code graphs, git lineage, and learned conventions wired in.

These docs are organised so you can move from “first install” to “deep integration” without backtracking. The left rail mirrors that progression.

Where to start

What is ACECode? The 2-minute overview: what problem it solves and how it works.

Quick Start From zero to your first semantic search in 5 minutes.

MCP Tools The 20+ tools your AI assistant can call once ACE is connected.

Pricing & Credits How credits work, what each tier includes, and how model choice affects cost.

Use ACECode with

Claude Code

Drop the MCP server URL into your config — Claude calls mcp__acecode__* tools automatically.

Cursor

Add ACE as an MCP server. Your Cursor chat gains semantic search across your entire codebase.

VS Code (ACE extension)

Inline code intelligence — see related symbols, recent changes, and relevant memories as you edit.

The CLI

ace search, ace index, ace watch — every MCP tool also has a CLI surface for scripting.

What’s in these docs

• Getting Started — install the CLI, register a project, run your first query.
• MCP Tools — reference for every tool exposed over the MCP protocol.
• CLI Reference — flags, examples, and exit codes for every ace subcommand.
• Billing & Credits — how the credit system works and which tier fits you.
• Deploy — self-host on your own infrastructure (Business tier).
• Integrations — Claude Code, Cursor, VS Code, and any MCP client.

Looking for something specific? Use the search box (/ to focus) or hit ⌘K to open Ask AI. If you can’t find what you need, open an issue or email support@acecode.dev.