Connect Edgaze MCP
Manual setup and agent installation for Cursor, Claude, ChatGPT, Codex, VS Code and GitHub Copilot, Gemini, Devin Desktop, OpenCode, and other MCP clients.
An agent installing Edgaze MCP, or a person doing the same by hand.
The client has a remote server at https://mcp.edgaze.ai, the human has approved access, and the five Edgaze tools are listed.
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 six tools: edgaze_catalog, edgaze_search, edgaze_inspect, edgaze_run, edgaze_watch, and edgaze_upload.
| Use | Value |
|---|---|
| Server | https://mcp.edgaze.ai |
| Consent host | https://www.edgaze.ai |
| Wallet | https://www.edgaze.ai/wallet |
| Markdown for agents | https://www.edgaze.ai/docs/mcp/connect.md |
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, Codex, VS Code, Devin Desktop, and OpenCode each use a different file and format. ChatGPT, Claude, Claude Desktop, and Gemini have no config file for remote servers: they connect from their own settings. If this is another client, use Other clients. If you cannot tell which client this is, ask.
Then:
- Follow the matching section below.
- Add Edgaze in that client's format. Keep any servers already in the file.
- Name the server
edgaze. - Do not add an API key, bearer token, or
Authorizationheader. Sign-in is the Edgaze browser OAuth flow the client starts. - Reload or restart the client if it requires that. Use that app's Connect or Sign in control. Do not open
/oauth/consentin a normal browser tab. - When the client opens consent, approve Find workflows and Run workflows.
- Confirm the
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. Do not add headers or an auth block: Edgaze signs you in with OAuth.
Then open Customize in the Cursor sidebar and make sure Edgaze is turned on. Disabled servers do not load. When Cursor asks you to sign in to Edgaze, do. Do not open /oauth/consent in a browser tab.
Claude Code#
Claude Code treats a server that has a url and no type as a local command, and it fails. The fastest user-scope add is:
claude mcp add --transport http --scope user edgaze https://mcp.edgaze.ai
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". User-scope servers are stored in ~/.claude.json.
Then sign in: run /mcp inside Claude Code and follow the browser steps, or run claude mcp login edgaze from your shell.
Claude#
This is claude.ai, Claude Desktop, Cowork, and the mobile apps. It is not Claude Code. Claude reaches Edgaze from Anthropic's servers, so localhost will not work. There is no config file to edit.
Open Customize → Connectors, click + Add, then Add custom connector. Enter the name Edgaze and the URL https://mcp.edgaze.ai, then continue. Keep the sign-in Claude detects. Do not add request headers or an API key.
Click Add. Claude 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, with the same URL. Members then open Customize → Connectors, find Edgaze under Custom, and click Connect.
Adding the connector does not enable it in every chat. In the conversation, open + → Connectors and turn Edgaze on.
Claude Desktop#
Claude Desktop connects to Edgaze the same way as claude.ai: add it from Customize → Connectors as in the Claude section above.
Do not add Edgaze to claude_desktop_config.json. That file only starts local command servers on your machine; an entry with a url is ignored or stops Claude Desktop from loading its servers.
ChatGPT#
This is ChatGPT on the web. It is not Codex, and ~/.codex/config.toml does not apply. There is no local config file to create. Workspace permissions apply: a managed workspace may need an admin to allow custom MCP servers.
Open ChatGPT Plugins, select the plus button, and choose Add custom MCP server:
- Name:
Edgaze - Description:
Find and run Edgaze marketplace workflows. - Server URL: https://mcp.edgaze.ai
Do not append /mcp or use a tunnel. For authentication choose OAuth. Do not paste an API key. Review the warning, select I understand and want to continue, then Create as a plugin. Install the plugin from your personal plugins, and approve Find workflows and Run workflows when Edgaze asks.
To use it, type @ in the message box and choose Edgaze. Confirmation before write-capable tools is expected.
Gemini#
This is the Gemini app: gemini.google.com on a computer, and the Gemini app on Android, iPhone, and iPad. Gemini reaches Edgaze from Google's servers, so there is no config file and localhost will not work.
Google's requirements for custom apps: you are 18 or over and in the US, you sign in with a personal Google Account (not a work or school account), Keep Activity is on, and you use Gemini in English.
On a computer#
You add Edgaze here. The mobile app cannot add a custom app, but it can use one you added on the web.
- Go to gemini.google.com. At the bottom, click Settings → Connected Apps. If you do not see Connected Apps, click Personal Intelligence → Connected Apps first.
- Under Custom apps, click Add a custom app.
- Enter the MCP server URL https://mcp.edgaze.ai. Leave Advanced features closed: Edgaze registers Gemini on its own, so there is no client ID or secret to enter.
- Click Next and follow the steps. Gemini opens Edgaze: sign in and approve Find workflows and Run workflows.
- In a chat, type
@and choose Edgaze.
On your phone#
- Add Edgaze on a computer first, as above.
- Open the Gemini app on Android, iPhone, or iPad, signed in to the same Google Account. Edgaze is already connected.
- In a chat, type
@and choose Edgaze.
Gemini asks you to confirm before any action that writes, such as starting a run.
Codex#
Codex uses TOML. Personal file: ~/.codex/config.toml. Trusted project file: .codex/config.toml.
[mcp_servers.edgaze] url = "https://mcp.edgaze.ai"
Do not set a bearer token or headers. Or run:
codex mcp add edgaze --url https://mcp.edgaze.ai
Then sign in:
codex mcp login edgaze
In the ChatGPT desktop app or the Codex IDE extension, you can select Authenticate in the server list instead. The desktop app, Codex CLI, and IDE extension share this file. ChatGPT on the web does not read it.
VS Code and GitHub Copilot#
This covers VS Code, VS Code Insiders, and the GitHub Copilot app. The fastest way is the GitHub MCP Registry:
- Open Edgaze in the GitHub MCP Registry.
- Press Install MCP server. Its menu offers Install in VS Code, Install in VS Code Insiders, and Install in GitHub Copilot app. Choose the app you use.
- The app opens with the Edgaze server ready to add. Press Install.
- Confirm that you trust the server so it can start, then sign in to Edgaze and approve Find workflows and Run workflows.
- In Copilot Chat, switch to Agent mode. Configure Tools lists the Edgaze tools.
To add it by hand instead, 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"
}
}
}You can also run MCP: Add Server, choose HTTP, and enter https://mcp.edgaze.ai. Then trust the server and sign in as in step 4.
Devin Desktop#
Windsurf is now Devin Desktop. Its servers live in mcp_config.json in the Devin config folder:
- macOS and Linux:
~/.config/devin/mcp_config.json - Windows:
%APPDATA%\devin\mcp_config.json
Open it from the Cascade panel: click the … menu at the top right, then Open MCP config file in the MCPs section. Add Edgaze under mcpServers and save:
{
"mcpServers": {
"edgaze": {
"serverUrl": "https://mcp.edgaze.ai"
}
}
}url is accepted in place of serverUrl. Then turn Edgaze on with its toggle in the MCPs section, and sign in when it asks. Do not add headers or an API key.
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 tools do not appear, add "timeout": 30000 to the edgaze object and try again.
Other clients#
Any MCP client that can add a remote streamable HTTP server can use Edgaze. Do not choose stdio or SSE: Edgaze serves streamable HTTP only, so a client that offers only SSE cannot connect. 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 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#
Consent says it is missing a sign-in request
Consent page looks wrong
/oauth/consent link is not a sign-in.Claude Code ignores the server
"type": "http". Without it, Claude Code treats the entry as a local command and it fails.VS Code ignores the server
"servers", not mcpServers, and the server needs "type": "http". Check that it is started and trusted under MCP: List Servers.Copilot has no Edgaze tools
Codex ignores the server
[mcp_servers.edgaze], not JSON.Cursor opens the Edgaze marketing site
Claude has no Edgaze tools
claude_desktop_config.json does not configure remote connectors anywhere, including Claude Desktop.Gemini has no Custom apps section
ChatGPT has no Edgaze tools
@ in the chat and choose Edgaze. Codex config.toml does not apply here.OpenCode ignores the server
mcp object with "type": "remote". Do not set "oauth": false.A run asks for money
Was this useful?
Your response helps us improve the documentation.