Skip to main content

Forge CLI MCP Server Guide & Browser Sign-In

This release adds the Forge CLI MCP server guide so Cursor, Claude Code, VS Code, and other coding agents can sign you in, call Digital Insight APIs, and build, preview, and submit widgets and Aspects through chat. Forge CLI login now supports web browser sign-in (including forge login --browser) and username and password in the terminal, with new browser sign-in troubleshooting. See What's New below for the per-guide list.

What's New​

Forge CLI MCP server​

  • New guide — Documents the MCP server that ships inside the Forge CLI, including beta scope and how it shares your CLI session with your coding agent.
  • How to install — Prerequisites, forge mcp install for Cursor and Claude Code, and per-agent setup for Cursor IDE, Cursor CLI, VS Code, Claude Code CLI, Claude Desktop, Codex CLI, Codex in the ChatGPT desktop app, GitHub Copilot CLI, Gemini CLI, and other coding agents (manual stdio config and PATH notes).
  • One-click install — Add to Cursor and Open in VS Code buttons on the guide use official install links.
  • Restart and sign in — Ask your agent to log you in; browser sign-in and MFA must finish within three minutes unless you are already signed in to the CLI.
  • What you can ask — Example prompts for apps, APIs, widget and Aspect preview, and submissions, with confirmation for destructive or write operations.
  • How to update — Upgrade the CLI (Homebrew, pnpm, or npm beta) and reload Forge in each agent.
  • MCP tools — Table of tools mapped to Forge CLI commands (sign-in, apps, APIs, docs, widgets, Aspects, playground, submissions, repository).
  • Troubleshooting — forge mcp doctor, forge mcp install --force, sign-in timeouts, SSH and remote browser limits, session expiry, credential store issues, and what to send the platform team (doctor reports and logs).

Forge CLI​

  • Command Reference — forge login documents interactive browser versus username and password sign-in; forge login --browser skips the prompt. The authentication flow explains the local callback, three-minute link expiry, OS credential store sharing with the MCP server, and console environment selection. New MCP server section covers forge mcp, forge mcp install, forge mcp install --client generic --print, forge mcp install --force, and forge mcp doctor.
  • Quick Start — Step 1 covers browser and terminal sign-in; new Step 7: Connect an AI assistant (optional) with forge mcp install and a link to the MCP guide.
  • Installation — Node.js >= 20 prerequisite. Optional Connect an AI assistant section points to forge mcp install and the Forge CLI MCP guide.
  • Troubleshooting — Quick-reference row for browser sign-in and Forge MCP issues; Browser sign-in for missing browser tabs, timeouts, and sign-in when the browser runs on a different machine than Forge (use username and password).

Get Started​

  1. Forge CLI MCP server — Run forge mcp install, restart your agent, and ask to log in to Forge.
  2. Forge CLI Quick Start — Sign in with forge login or forge login --browser, then optional Step 7 for MCP.
  3. Forge CLI Command Reference — MCP server — Commands your assistant runs in the background.
  4. Browser sign-in troubleshooting — If the callback never returns or you develop over SSH.

The Candescent Developer Experience Team