Skip to content

# Cursor

Cursor has its own built-in codebase indexing, but CCE adds compressed retrieval and token savings tracking on top.

## Quick setup

Section titled “Quick setup”
Terminal window

    cce init              # Auto-detects Cursor if .cursor/ existscce init --agent all  # Explicitly includes Cursor

## Files created

Section titled “Files created”

### `.cursor/mcp.json`

Section titled “.cursor/mcp.json”

Registers the CCE MCP server for Cursor’s agent mode.

    {  "mcpServers": {    "context-engine": {      "command": "cce",      "args": ["serve"]    }  }}

### `.cursorrules`

Section titled “.cursorrules”

Contains instructions for Cursor’s AI to prefer `context_search` over raw file reads. The CCE block is wrapped in markers so your own rules are preserved.

## Working with Cursor’s built-in indexing

Section titled “Working with Cursor’s built-in indexing”

Cursor indexes your codebase for its own retrieval. CCE complements this by:

- Providing compressed context that uses fewer tokens per query.
- Tracking token savings so you can measure cost reduction.
- Offering graph-aware retrieval that follows code relationships.

Both systems can run side by side without conflict.

## Restarting after setup

Section titled “Restarting after setup”

After running `cce init`, restart Cursor to pick up the new MCP server configuration.