vestige/docs/integrations/cursor.md
2026-04-05 18:50:57 +03:00

2.8 KiB

Cursor

Give Cursor a brain that remembers between sessions.

Cursor has native MCP support. Add Vestige and your AI assistant remembers your architecture, preferences, and past fixes across every session.


Setup

1. Create or edit the config file

Global (all projects):

Platform Path
macOS / Linux ~/.cursor/mcp.json
Windows %USERPROFILE%\.cursor\mcp.json
# macOS / Linux
mkdir -p ~/.cursor
open -e ~/.cursor/mcp.json

2. Add Vestige

{
  "mcpServers": {
    "vestige": {
      "command": "/usr/local/bin/vestige-mcp",
      "args": [],
      "env": {}
    }
  }
}

Use absolute paths. Cursor does not reliably resolve relative paths or ~. Run which vestige-mcp to find your binary location.

Windows:

{
  "mcpServers": {
    "vestige": {
      "command": "C:\\Users\\you\\.cargo\\bin\\vestige-mcp.exe",
      "args": [],
      "env": {}
    }
  }
}

3. Restart Cursor

Fully quit and reopen Cursor. The MCP server loads on startup.

4. Verify

Open Cursor's AI chat and ask:

"What MCP tools do you have access to?"

You should see Vestige's tools listed (search, smart_ingest, memory, etc.).


First Use

Ask Cursor's AI:

"Remember that this project uses React with TypeScript and Tailwind CSS"

Start a new chat session, then:

"What tech stack does this project use?"

It remembers.


Project-Specific Memory

To isolate memory per project, use --data-dir:

{
  "mcpServers": {
    "vestige": {
      "command": "/usr/local/bin/vestige-mcp",
      "args": ["--data-dir", "/Users/you/projects/my-app/.vestige"],
      "env": {}
    }
  }
}

Or place a .cursor/mcp.json in the project root for project-level config.


Troubleshooting

Vestige tools not appearing
  1. Verify the binary exists:
    which vestige-mcp
    
  2. Test the binary manually:
    echo '{}' | vestige-mcp
    
  3. Check the config is valid JSON:
    cat ~/.cursor/mcp.json | python3 -m json.tool
    
  4. Fully restart Cursor (Cmd+Q / Alt+F4, not just close window).
Silent failures

Cursor does not surface MCP server errors in the UI. Test by running the command directly in your terminal to see actual error output.


Also Works With

IDE Guide
Xcode 26.3 Setup
Codex Setup
VS Code (Copilot) Setup
JetBrains Setup
Windsurf Setup
Claude Code Setup
Claude Desktop Setup

Your AI remembers everything, everywhere.