Connecting AI Apps & Editors (MCP)
Connect your AI chat app, IDE, or CLI agent to Glow over the Model Context Protocol (MCP). Your client can inspect your workspace, build automations on a live canvas, read traces, save versions, and run tests.
- Use it to
- Connect ChatGPT, Claude, Gemini, Cursor, VS Code, Zed, Windsurf, Claude Code, Codex CLI, or Gemini CLI via OAuth 2.1 or a personal token
- Find it
- Workflow Assistant header → Connect AI tool, or Your account → MCP (/app/user/account?tab=mcp)
- Cost
- Free to connect, inspect, build drafts, and validate · Tests use shared workspace balances
- Limits
- Requires Admin, Manager, or Member role · Up to 25 active OAuth app and personal token connections per user · Optional 100-automation allowlist
Supported Clients at a Glance
- Used by ChatGPT, Claude, Gemini, Cursor, VS Code, Zed, Claude Code, Codex CLI, and Gemini CLI.
- Connect to https://api.getglow.ai/mcp and choose your workspace and preset in the browser.
- Update permissions, workspace scope, or Data Store access in place without reconnecting.
- Used by Windsurf, local JSON/TOML configs, and custom Streamable HTTP clients.
- Create in Your account → MCP (+ Create token) and pass Authorization: Bearer <token>.
- Supports independent regeneration, 90-day renewal, and 100-automation allowlists.
| Client | Category | Setup Path |
|---|---|---|
| ChatGPT | Chat & AI apps | Plugins → + → Add custom MCP server → paste Server URL → sign in. |
| Claude | Chat & AI apps | Customize → Connectors → + Add → Add custom connector → paste URL → sign in. |
| Google Gemini | Chat & AI apps | Settings → Connected Apps → Add a custom app at gemini.google.com → @Glow. |
| Cursor | IDEs & developer tools | Click Add to Cursor (OAuth), or add token to ~/.cursor/mcp.json. |
| VS Code | IDEs & developer tools | Click Add to VS Code (OAuth), or add token to .vscode/mcp.json. |
| Zed | IDEs & developer tools | Click Copy setup & Open Zed and add URL in settings.json. |
| Windsurf | IDEs & developer tools | Click Create token & copy configuration and paste into mcp_config.json. |
| Claude Code | IDEs & developer tools | Run claude mcp add --transport http --scope user glow https://api.getglow.ai/mcp. |
| Codex CLI | IDEs & developer tools | Run codex mcp add glow --url https://api.getglow.ai/mcp and codex mcp login glow. |
| Gemini CLI | IDEs & developer tools | Run gemini mcp add --transport http --scope user glow https://api.getglow.ai/mcp. |
| Other MCP clients | IDEs & developer tools | Connect to https://api.getglow.ai/mcp via OAuth 2.1 + PKCE or Bearer <token>. |
Where to Open Quick Connect
You need an Admin, Manager, or Member role in an MCP-enabled workspace.
- Click Connect AI tool in the Workflow Assistant header, welcome card, or More (⋯) menu.
- Switch between Chat & AI apps and IDEs & developer tools on the canvas.
- Click Full MCP settings & token management to manage existing connections.
- Open Your account → MCP (/app/user/account?tab=mcp) or Team settings → MCP → My MCP connection.
- Launch one-click IDE installers, copy the Server URL, or mint personal tokens.
- Manage up to 25 active connections with in-place permission edits and Pause all.
Connect Chat & AI Apps (Sign In with Glow)
ChatGPT, Claude, and Google Gemini use OAuth 2.1 + PKCE. Copy the Server URL (https://api.getglow.ai/mcp) from Your account → MCP. Never paste a browser canvas URL (https://app.getglow.ai/...).
ChatGPT
ChatGPT
Copy the Server URL and open ChatGPT
Click Copy URL & Open ChatGPT in Quick Connect to open ChatGPT Plugins .
Add the custom MCP server
Open Plugins → + → Add custom MCP server and paste https://api.getglow.ai/mcp.
Sign in with Glow and choose permissions
Pick your workspace and preset (Build drafts (Recommended) by default). Click Allow access.
First time using Glow? Signing in during MCP OAuth without an account creates your first Free workspace automatically. Keep Open Glow in a new tab to watch your automation build checked for live canvas updates.
Editor Configuration Guides
Switch Quick Connect to IDEs & developer tools for one-click installers, browser OAuth sign-in, or personal token snippets.
Cursor
Cursor
Option 1: One-click OAuth install (Recommended). Click Add to Cursor in Quick Connect to install glow and sign in via browser.
Option 2: Personal token in ~/.cursor/mcp.json. Add this snippet and check Cursor Settings → MCP:
{
"mcpServers": {
"glow": {
"url": "https://api.getglow.ai/mcp",
"headers": { "Authorization": "Bearer PASTE_YOUR_GLOW_MCP_TOKEN_HERE" }
}
}
}Live Canvas Companion & In-Chat Account Links
- Companion canvas (
?source=mcp): Workflow tools returncanvasUrl,canvasMarkdownLink, and a Workflow Card (ui://glow/workflow). Companion mode keeps the Workflow Assistant drawer closed and suppresses build banners. - Automatic tab following: An idle Glow tab switches to the edited automation automatically and frames new Steps with
fitView. - One-click account links (
?source=mcp&connectStep=N):get_connectionsandget_workflowreturnconnectUrlandconnectMarkdownLink. Clicking opens that Step’s connection dialog and binds matching sibling Steps.
Manage Connections, Presets, and Scoped Tokens
Create a Scoped Token or Authorize an App
-
Open Your account → MCP or Team settings → MCP → My MCP connection. Click + Create token to mint a manual
glow_mcp2_…token. -
Pick a Permissions level and Workspaces scope (Only
{Workspace}, All my workspaces for Admins, or Limit to specific automations up to 100 automations). When your client asks for tool approval, Choose “Always allow” for read tools only. Ask every time before running or changing automations:Permission Level Tools in tools/listWhat It Allows Read only 16Inspect automations, schemas, and run history. Nothing can be changed or run ( readData Store access in tests).Build drafts (Recommended) 25(22on legacy no-test)Default for new tokens, OAuth sign-in, and Quick Connect. Read all automations, create/edit drafts, and test drafts ( test_step,run_workflow_test).Full access 25(26withManages Live)Everything in Build drafts, plus Live tests and writeData Store test access by default. Live edits require Manage Live automations. -
Set the optional checkboxes and Data stores test level (
None,Read, orWrite) below the permission levels:- Allow tests to use workspace secrets (Tests use secrets badge): lets MCP tests read
{{ $secret.* }}and{{ $key.* }}. Without it, Steps needing an unapproved secret fail withMCP_TEST_SECRETS_REFUSED. - Manage Live automations (Manages Live badge for Admins on Full access): lets the connection edit, publish, or pause Live automations (
set_workflow_status).
- Allow tests to use workspace secrets (Tests use secrets badge): lets MCP tests read
-
Click Generate token (or Allow access on OAuth consent). Each user can keep up to 25 active connections. Connections expire 90 days after creation or renewal, or after 30 idle days (with a 7-day email warning and Renew).
Change Permissions, Renew, or Pause in Place
- Click Change permissions in Your account → MCP to switch between Read only, Build drafts, and Full access.
- Adjust the Data stores test level (
None,Read,Write), workspace scope, or 100-automation allowlist without reconnecting. - Toggle Allow tests to use workspace secrets or Manage Live automations, click Renew for 90 days, or click Pause all. Start a new chat after changing permissions so your client refreshes
tools/list.
Verify Read Access
Ask your AI client to call list_workflows or run /build-automation, /explain-automation, /optimize-automation, /debug-failed-run, or /test-and-verify-draft. Discovery, validation, and direct edits cost zero credits.
Troubleshooting
| Symptom | Check and Next Action |
|---|---|
401 or authentication fails | Re-authenticate OAuth or update Authorization: Bearer … if a token was regenerated, revoked, or expired (90 days or 30 days idle). |
list_workspaces is empty | Check workspace scope in Your account → MCP, confirm your Admin, Manager, or Member role, and verify MCP is not paused. |
workspace_not_authorized or workflow_not_authorized | Pass IDs from list_workspaces and list_workflows, or click Change permissions to update the workspace or 100-automation allowlist. |
| A write or testing tool is missing or refused | Check the preset in Your account → MCP and Maximum MCP permission in Team settings → MCP, then start a new chat. |
active_workflow_protected | Edit a draft instead. Live edits require Full access, Manage Live automations, workspace Allow Live changes, Admin role, and allowActiveWorkflowMutation: true. |
token_limit_reached (max 25 active connections) | Revoke an unused connection in Your account → MCP or reuse an existing entry via Change permissions / Regenerate. |
Client returns HTML or 404 when connecting | Use the MCP Server endpoint (https://api.getglow.ai/mcp), never a browser canvas URL (https://app.getglow.ai/...). |
| A test times out, loses its response, or is unavailable | Follow Step recovery, whole-run recovery, or availability guidance. |
For failed automation runs, see Troubleshooting & Common Errors. Keep tokens and secrets out of support messages.
- Run
- In your connected AI client, ask: Call list_workspaces in Glow
- You should see
- The client returns your Glow workspace name, role, and current Step credit and Glow AI token balances.
What’s Next?
- 👉 Build and validate with MCP tools before testing the automation.
- MCP Administration: configure workspace budgets and access restrictions.