Skip to main content

Cursor

Cursor is an AI-first code editor built on VS Code. It supports MCP servers through JSON configuration files.

Configuration​

Cursor supports two configuration levels:

ScopeLocationUse Case
Global~/.cursor/mcp.jsonAvailable in all projects
Project.cursor/mcp.json in project rootProject-specific

Choose the configuration based on whether you have the Desktop App or VS Code Extension installed.

Desktop App​

If you have the SF Veritas Desktop App installed:

macOS​

{
  "mcpServers": {
    "sailfishTelemetry": {
      "command": "node",
      "args": ["/Applications/SF Veritas.app/Contents/Resources/app.asar.unpacked/dist/mcp-server/index.js"]
    }
  }
}

Windows​

{
  "mcpServers": {
    "sailfishTelemetry": {
      "command": "node",
      "args": ["%LOCALAPPDATA%\\Programs\\SF Veritas\\resources\\app.asar.unpacked\\dist\\mcp-server\\index.js"]
    }
  }
}

Linux​

{
  "mcpServers": {
    "sailfishTelemetry": {
      "command": "node",
      "args": ["/opt/SF Veritas/resources/app.asar.unpacked/dist/mcp-server/index.js"]
    }
  }
}

VS Code Extension​

If you have the SF Veritas VS Code Extension installed:

macOS / Linux​

{
  "mcpServers": {
    "sailfishTelemetry": {
      "command": "bash",
      "args": ["-c", "node \"$(ls -d ~/.vscode/extensions/sailfish-ai.sf-veritas-extension-* 2>/dev/null | sort -V | tail -1)/dist/mcp-server-bundled.js\""]
    }
  }
}

This command:

  • Uses glob pattern to find the extension (no hardcoded version)
  • Sorts by version and picks the latest if multiple exist
  • Uses bash -c to handle path expansion

Windows​

{
  "mcpServers": {
    "sailfishTelemetry": {
      "command": "cmd",
      "args": ["/c", "for /d %d in (%USERPROFILE%\\.vscode\\extensions\\sailfish-ai.sf-veritas-extension-*) do @node \"%d\\dist\\mcp-server-bundled.js\""]
    }
  }
}

Enabling MCP in Cursor​

MCP must be enabled in Cursor settings:

  1. Open Cursor Settings (Cmd+, on macOS, Ctrl+, on Windows/Linux)
  2. Search for "MCP"
  3. Ensure MCP Servers is enabled

You can also access MCP settings via:

  • Command Palette (Cmd+Shift+P) → "Cursor Settings: Open MCP Settings"

Agent Mode Requirement​

Important: MCP tools only work in Cursor's Agent mode, not in normal chat.

To use MCP tools:

  1. Open the AI pane (Composer)
  2. Switch to Agent mode using the mode selector
  3. Now the telemetry tools are available

Verification​

After configuring, verify the connection:

  1. Reload Cursor window (Cmd+Shift+P → "Reload Window")
  2. Open Command Palette (Cmd+Shift+P)
  3. Search for "MCP: List Servers" or check MCP settings
  4. You should see sailfishTelemetry in the list
  5. Check the Output panel → "MCP Logs" for connection status

Usage​

Once connected, use Agent mode to query telemetry:

> List my recent telemetry sessions
> Show me errors from the last session
> What are the performance bottlenecks in my app?
> Trace the execution of the handleSubmit function

Cursor will use the MCP tools to analyze your application's behavior.

Troubleshooting​

Server not appearing in MCP settings​

  1. Ensure the config file is in the correct location
  2. Verify JSON syntax is valid
  3. Reload Cursor window
  4. Check Output → "MCP Logs" for errors

MCP tools not available in chat​

Make sure you're in Agent mode, not normal chat mode. MCP tools are only available in Agent mode.

"No telemetry data found"​

  1. Ensure your application has been instrumented with SF Veritas SDK
  2. Run your application to generate telemetry data
  3. Check that the database exists: ls ~/.sailfish/telemetry.db