StableAdapters

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)

Install

forg connect cursor

This registers a managed FORG MCP server entry, backed bynpx -y forg-mcp@latest, in ~/.cursor/mcp.json undermcpServers.forg. Restart Cursor afterwards so it reloads the config and starts the FORG MCP server. The entry is idempotent and marked as FORG-managed, soforg uninstall removes only the FORG footprint.

What gets captured

Cursor Composer interactions (model, tokens, cost, latency)
Cursor Chat messages and responses
Agent mode tool calls (each tool = one signal)
Auto-sampled session heartbeats (every 30 s for standalone hosts)

Verification

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

# From a terminal:
forg status
# then start a new Cursor session and confirm signals arrive

Troubleshooting

Issue	Resolution
MCP server shows "disconnected"	Ensure Node.js 18+ is installed and on PATH (the entry runs `npx -y forg-mcp@latest`), then restart Cursor.
Signals appear but cost_usd is 0	Cursor does not expose cost data via MCP. FORG estimates cost from model pricing tables.
Inline completions not tracked	Cursor's inline completion API is not exposed via MCP. Only Composer, Chat, and tool calls are tracked.

Known limitations

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