Connect Edgaze MCP

Edgaze MCP is a remote HTTP server at https://mcp.edgaze.ai. Do not add it as a local command, npx package, or stdio wrapper. After you connect, the client starts OAuth, you approve access, and the client should list five tools: edgaze_catalog, edgaze_search, edgaze_inspect, edgaze_run, and edgaze_watch.

Do not open https://www.edgaze.ai/oauth/consent yourself. A bare consent link has no sign-in request. The client starts OAuth after it reaches the server, then opens that page.

A zero wallet is normal after install. Do not start a paid workflow from this page. When you want a run, go to Your first run.

For agents#

Identify the MCP client first. Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and OpenCode each use a different file and format. ChatGPT and the Claude app have no local config file. If this is another client, use Other clients. If you cannot tell which client this is, ask.

Then:

1. Follow the matching section below.
2. Add Edgaze in that client's format. Keep any servers already in the file.
3. Name the server edgaze.
4. Do not add an API key, bearer token, or Authorization header. Sign-in is the Edgaze browser OAuth flow the client starts.
5. Reload or restart the client if it requires that. Use that app's Connect or Sign in control. Do not open /oauth/consent in a normal browser tab.
6. When the client opens consent, approve Find workflows and Run workflows.
7. Confirm the five edgaze_* tools are listed.

Cursor#

Project file: .cursor/mcp.json. Personal file: ~/.cursor/mcp.json. If both define edgaze, the project file wins.

{
  "mcpServers": {
    "edgaze": {
      "url": "https://mcp.edgaze.ai"
    }
  }
}

A url is remote, so do not add a command. type is optional. You can also use Cursor Settings → Tools & MCP → New MCP Server and enter https://mcp.edgaze.ai. Enable the server if the toggle is off. If Cursor shows Connect or Sign in, use that. Do not open /oauth/consent in a browser tab.

Claude Code#

Claude Code skips a remote server that has a url and no type. The fastest user-scope add is:

claude mcp add --transport http edgaze https://mcp.edgaze.ai --scope user

For a shared project file, add .mcp.json at the repository root:

{
  "mcpServers": {
    "edgaze": {
      "type": "http",
      "url": "https://mcp.edgaze.ai"
    }
  }
}

"type": "streamable-http" is accepted as an alias for "http". The same server object can go under mcpServers in ~/.claude.json.

If sign-in does not open on its own, run /mcp and start it there.

Claude#

This is claude.ai, iOS, Android, Cowork, and remote connectors in Claude Desktop. It is not Claude Code. Claude reaches Edgaze from Anthropic's servers, so localhost will not work. There is no local config file to create.

Open Customize → Connectors → Add custom connector. Use https://mcp.edgaze.ai. Leave Advanced OAuth Client ID and Client Secret empty. Do not add request headers or an API key.

Click Add, then Connect. Claude starts OAuth and opens consent on www.edgaze.ai. Approve Find workflows and Run workflows. Free accounts can add one custom connector.

On Team and Enterprise, an Owner adds Edgaze first from Organization settings → Connectors → Add → Custom → Web, with the same URL and empty secrets. Members then open Customize → Connectors and click Connect.

Adding the connector does not enable it in every chat. In the conversation, open + → Connectors and turn Edgaze on. claude_desktop_config.json does not configure claude.ai, Cowork, mobile, or Claude's remote connector system.

Claude Desktop#

Use this only when you want the local Desktop config file. For claude.ai, Cowork, mobile, or remote Desktop connectors, use the Claude section above.

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

{
  "mcpServers": {
    "edgaze": {
      "url": "https://mcp.edgaze.ai"
    }
  }
}

Fully quit and reopen Claude Desktop after you edit the file. If it asks for a transport, choose remote HTTP and https://mcp.edgaze.ai.

ChatGPT#

This is ChatGPT on the web and the ChatGPT iOS and Android apps. It is not Codex, and ~/.codex/config.toml does not apply. There is no local config file to create.

Turn on Settings → Security and login → Developer mode. That needs a Plus, Pro, Business, Enterprise, or Edu account. A managed workspace may also need an admin to allow it.

Then open ChatGPT Plugins or Settings → Plugins and create a developer-mode app:

• Name: Edgaze
• Description: Find and run Edgaze marketplace workflows.
• Connection: Public HTTPS
• Server URL: https://mcp.edgaze.ai

Do not append /mcp or use a tunnel. Choose OAuth. Do not choose Token or paste an API key. Leave client ID and client secret empty. After you create the connection, approve Find workflows and Run workflows. The app appears under Drafts.

Saving the plugin does not enable it in a chat. Start a new conversation, open the Plus menu, choose Developer mode, and turn Edgaze on. You can then ask ChatGPT to use Edgaze by name. Confirmation before write-capable tools is expected.

Codex#

Codex uses TOML. Personal file: ~/.codex/config.toml. Trusted project file: .codex/config.toml.

[mcp_servers.edgaze]
url = "https://mcp.edgaze.ai"

Leave auth unset. Do not set a bearer token. Or run:

codex mcp add edgaze --url https://mcp.edgaze.ai

The ChatGPT desktop app, Codex CLI, and Codex IDE extension share this file. Start OAuth from the Codex MCP panel, or from the next turn that needs Edgaze. ChatGPT on the web and mobile does not read this file.

VS Code#

VS Code uses a top-level servers object, not mcpServers, and remote servers need "type": "http". Workspace file: .vscode/mcp.json. Personal file: Command Palette → MCP: Open User Configuration.

{
  "servers": {
    "edgaze": {
      "type": "http",
      "url": "https://mcp.edgaze.ai"
    }
  }
}

Switch Copilot Chat to Agent mode. A temporary chat mention does not persist. You can also run MCP: Add Server, choose HTTP, and enter https://mcp.edgaze.ai.

Windsurf#

Windsurf Cascade reads ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "edgaze": {
      "serverUrl": "https://mcp.edgaze.ai"
    }
  }
}

Some builds accept url instead of serverUrl. Then open Settings → Cascade → MCP and enable Edgaze.

OpenCode#

OpenCode uses opencode.json or opencode.jsonc at the repo root, or ~/.config/opencode/opencode.json for a personal config. The project file wins if both define edgaze. It does not read .cursor/mcp.json or a top-level mcpServers object.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "edgaze": {
      "type": "remote",
      "url": "https://mcp.edgaze.ai"
    }
  }
}

"type": "remote" is required. Do not add headers, an API key, or "oauth": false. OpenCode starts OAuth when oauth is left unset.

You can also add it from the CLI. Choose a remote server, name it edgaze, and enter https://mcp.edgaze.ai:

opencode mcp add

Then authenticate:

opencode mcp auth edgaze

If the browser does not open, run that auth command again. Confirm the connection with:

opencode mcp list

If the server connects but the five tools do not appear, add "timeout": 30000 to the edgaze object and try again.

Other clients#

Any MCP client that can add a remote HTTP server (sometimes called streamable HTTP) can use Edgaze. Do not choose stdio. Use SSE only if the client has no HTTP option. If a client can only launch a local command, it cannot connect.

Add a server named edgaze. Point it at https://mcp.edgaze.ai. Do not add an API key, bearer token, Authorization header, or extra path.

If the client asks for a transport type, choose HTTP. Some files want "type": "http". Some want url. Some want serverUrl. Use the field that client already uses for remote servers.

{
  "url": "https://mcp.edgaze.ai"
}

Reload or restart if the client requires that. When the client starts OAuth, the browser should open consent on https://www.edgaze.ai with a sign-in request. Sign in and press Authorize. Opening /oauth/consent yourself will say the link is missing a request. A redirect to the Edgaze domain without www can look like a failed login even when the password is correct. You can create an account during this flow. You do not need to own or publish a workflow.

Approve Find workflows and Run workflows. The install is done when the five edgaze_* tools are listed. If tools are missing, check that Edgaze is enabled, the config was reloaded, and you are in the right client. Then ask the agent to find a workflow. See Your first run. An empty wallet is not a failed install. Add funds from Wallet when you want a paid run.

Troubleshooting#