Cursor Adapter

The Cursor adapter connects Cursor IDE to FORG using Cursor's MCP (Model Context Protocol) server integration. It captures every AI interaction in the Cursor composer, chat, and inline completions.

Prerequisites

• Cursor 0.42.0 or later (MCP support required)
• FORG CLI installed and activated
• Node.js 18+ (for the MCP server process)

Installation

Install the FORG MCP adapter globally:

npm install -g @forg-pro/mcp-adapter

Then configure Cursor to use it. Open Cursor settings (Cmd+,) and navigate to Features → MCP Servers, or edit ~/.cursor/mcp.json directly:

{
  "mcpServers": {
    "forg": {
      "command": "forg-mcp",
      "args": [],
      "env": {}
    }
  }
}

What gets captured

• All Cursor Composer interactions (model, tokens, cost, latency)
• Cursor Chat messages and responses
• Agent mode tool calls (each tool = one signal)
• Inline completions (when sampling data is available from Cursor)

Verification

# In Cursor, open the MCP panel (Cmd+Shift+P → "MCP: Show Servers")
# "forg" should appear as "connected"

# From terminal:
forg status --adapter
# Adapter:    forg-mcp (connected)
# Last signal: 8s ago

Configuration

Set environment variables in ~/.cursor/mcp.json under env:

{
  "mcpServers": {
    "forg": {
      "command": "forg-mcp",
      "args": [],
      "env": {
        "FORG_PROJECT_ID": "proj_my-cursor-work",
        "FORG_LOG_LEVEL": "debug"
      }
    }
  }
}

Troubleshooting

Known limitations

• Cursor does not expose inline completion data via MCP; only Composer/Chat signals are captured
• Cost estimates may differ slightly from Cursor's own billing due to pricing table lag
• Business plan Cursor accounts with model routing may show mixed model data per session