Edgaze MCP

Let your agent call a marketplace workflow directly as a tool.

Paste this to your agent

Fetch https://www.edgaze.ai/docs/mcp/connect.md and follow it to enable Edgaze MCP in this environment. Use only https://mcp.edgaze.ai as the server URL. Write the config this client expects, or follow the in-app connector steps if this client has no config file. Do not open https://www.edgaze.ai/oauth/consent yourself. After the client connects, it starts OAuth and opens consent with a sign-in request. Approve Find workflows and Run workflows there, then confirm the five Edgaze tools are available.

Audience

Anyone who wants their AI app to run Edgaze workflows.

Outcome

Paste one prompt, or write the config yourself, then sign in and run.

Edgaze MCP is how an AI app talks to the Edgaze marketplace. After you connect, the agent can search published workflows, read the input form and the price, start a run, and bring the result back into the chat.

It runs the same published product a human runs on the marketplace. There is no second graph and no rebuild.

Works with#

These clients can connect to Edgaze MCP. Open one for the exact setup. Other clients use the same remote server.

For your agent#

The box at the top of this page is the prompt to paste. It tells the agent to fetch Connect Edgaze MCP at https://www.edgaze.ai/docs/mcp/connect.md and write the config for this client. That page is the playbook. Humans can follow the same steps by hand.

What to use, exactly#

Use this	Do not substitute
Server `https://mcp.edgaze.ai`	`www.edgaze.ai`, `api.edgaze.ai`, or a localhost URL
Consent host `https://www.edgaze.ai`	Opening `/oauth/consent` yourself, or the apex host
Wallet `https://www.edgaze.ai/wallet`	A different billing page

A www mismatch on consent looks like a broken login. The client starts OAuth. Do not open /oauth/consent yourself. The agent must not invent a different server URL.

What you approve#

The app opens the Edgaze consent page. Sign in with your Edgaze account and allow:

Find workflows: see published names, prices, and input forms
Run workflows: start a demo or a paid run from your wallet

That is the whole grant. You can disconnect later from Settings → Connected apps.

What the agent can do#

Five tools, in this order:

edgaze_catalog: browse published categories when the goal is still vague
edgaze_search: find workflows for a job. If nothing matches, it stops
edgaze_inspect: read one slug: inputs, example values, price, whether a demo is available
edgaze_run: start the run. demo: true only when inspect said a demo is available
edgaze_watch: read output until the run finishes

The agent should inspect before it runs, show you the price, and use your words for the inputs. It should not invent values the form rejects. Text and external actions come back in the chat. Images, files, and other media come back as a link to the hosted run page on Edgaze.

After you connect#

A zero wallet is normal the first time. That is not a failed install. Open Wallet, add money when you want a paid run, and ask the agent to try again. See Wallet and Your first run.

If you publish workflows, agents run the same version marketplace buyers run. See For creators.

Next#

Connect Edgaze MCP: client setup and the agent playbook
Your first run
Wallet
For creators

Was this useful?

Your response helps us improve the documentation.

Set up Edgaze MCP

Fetch https://www.edgaze.ai/docs/mcp/connect.md and follow it to enable Edgaze MCP in this environment. Use only https://mcp.edgaze.ai as the server URL. Write the config this client expects, or follow the in-app connector steps if this client has no config file. Do not open https://www.edgaze.ai/oauth/consent yourself. After the client connects, it starts OAuth and opens consent with a sign-in request. Approve Find workflows and Run workflows there, then confirm the five Edgaze tools are available.

What to use, exactly#

Use this	Do not substitute
Server `https://mcp.edgaze.ai`	`www.edgaze.ai`, `api.edgaze.ai`, or a localhost URL
Consent host `https://www.edgaze.ai`	Opening `/oauth/consent` yourself, or the apex host
Wallet `https://www.edgaze.ai/wallet`	A different billing page

A www mismatch on consent looks like a broken login. The client starts OAuth. Do not open /oauth/consent yourself. The agent must not invent a different server URL.

What the agent can do#

Five tools, in this order:

edgaze_catalog: browse published categories when the goal is still vague

edgaze_search: find workflows for a job. If nothing matches, it stops

edgaze_inspect: read one slug: inputs, example values, price, whether a demo is available

edgaze_run: start the run. demo: true only when inspect said a demo is available

edgaze_watch: read output until the run finishes