Cursor

Cursor reads MCP server config from .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global). Remote MCP support is built in — no extra extensions.

Prerequisites

Cursor v0.49 or later
A Forvibe API key from Settings → API Keys

Setup

Add the server to your config

Inside your project root, create .cursor/mcp.json (or edit ~/.cursor/mcp.json for a machine-wide config). Cursor detects HTTP servers by the presence of a url field — no type or transport is needed:

json

{
  "mcpServers": {
    "forvibe": {
      "url": "https://www.forvibe.app/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FORVIBE_API_KEY}"
      }
    }
  }
}

Then export the key in your shell (~/.zshrc / ~/.bashrc):

bash

export FORVIBE_API_KEY="fvk_live_..."

Keeping the secret in an env var means .cursor/mcp.json is safe to commit and share with your team. Cursor interpolates ${env:VAR} references at load time.

Reload Cursor

Cmd-Shift-P → Developer: Reload Window (or fully quit and reopen). Cursor picks up the new MCP server on next launch.

Confirm in MCP panel

Cursor Settings → MCP → you should see forvibe listed with a green status dot and all 36 tools enabled.

Verify

In Composer or Chat (agent mode), ask: "List my Forvibe projects." Cursor will call list_projects (with an optional approval prompt the first time).

Cursor's January 2026 update added dynamic tool-context loading — having all 36 Forvibe tools connected only adds ~5% token overhead on average. Leave the connector on by default.