Claude Desktop

Add Forvibe MCP to Claude Desktop (Mac, Windows).

Updated 2026-05-12
3 min read

Claude Desktop supports remote MCP servers via the built-in Connectors UI (with OAuth) or via the config file (with a Bearer API key). Pick whichever fits your plan and workflow.

Option A — Connectors UI (OAuth)

Available on Pro, Max, Team, and Enterprise plans. The cleanest setup — no key handling, no config file.

1

Open the Connectors panel

Claude Desktop → Settings → Connectors → Add custom connector.

2

Enter Forvibe's URL

Fill the form:

  • Name: Forvibe
  • Remote MCP server URL: https://www.forvibe.app/mcp
  • Leave OAuth Client ID / Secret blank — Forvibe supports Dynamic Client Registration.
3

Approve in browser

Claude opens a Forvibe consent screen in your browser. Sign in if you're not already, review the permissions, click Approve. You'll bounce back to Claude as a connected connector.

Option B — Config file (API key)

Available on every Claude plan. Mint an API key first from Settings → API Keys.

1

Open the config file

Path:

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Create the file if it doesn't exist.

2

Add Forvibe under mcpServers

json
{
  "mcpServers": {
    "forvibe": {
      "url": "https://www.forvibe.app/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer fvk_live_..."
      }
    }
  }
}
3

Restart Claude Desktop

Quit Claude Desktop fully (Cmd+Q on Mac) and reopen. Settings → Developer should show forvibe as connected.

Verify

Start a new conversation and ask: "Use Forvibe to list my projects." Claude should call list_projects (you may be prompted to allow the first tool call).

If forvibe doesn't appear after restart, check the Claude Desktop log file (~/Library/Logs/Claude/mcp.log on Mac) for parsing or auth errors.