Use Edgible with an AI assistant

An AI assistant can look after your applications with you: list them, read their configuration, status and logs, and work out why a deploy is stuck. It connects to Edgible’s hosted MCP server and signs in as you, one organization at a time. There is no key to copy and nothing to install.

https://mcp.edgible.com/mcp

Hosted connections can read but not change anything. To let an assistant change or redeploy applications, run the local server with --allow-write.

Connect your assistant

Assistant	How you add Edgible	Setup
Claude (claude.ai, Claude Desktop, the mobile apps)	A custom connector	Claude
Claude Code	One command	Claude Code
Cursor	One-click install	Cursor
VS Code (GitHub Copilot)	One-click install	VS Code
ChatGPT	A custom MCP server	ChatGPT
Any other client that supports remote MCP servers	The URL	Other clients

The AI assistants page in the Edgible console (under Account) shows the same URL, with a copy button, install links and the steps for each assistant.

The first time an assistant connects, it sends you to Edgible in your browser:

1. Sign in to Edgible, if you aren’t already.
2. The page reads Connect assistant to Edgible. Pick the organization the assistant may use and read what it will be able to do.
3. Choose Allow. The browser goes back to the assistant, which can now use Edgible.

Edgible asks every time an assistant connects, even one you allowed before.

Apps Edgible can’t verify

Some apps publish their details on their own domain, and Edgible knows the domains of the big ones: claude.ai (Claude and Claude Code), vscode.dev (VS Code) and chatgpt.com. For those the page shows a Verified domain under the app’s name. Other apps, Cursor among them, register themselves under a name they choose, or publish their details on a domain Edgible doesn’t know. For those the page says Edgible can’t verify this app and the button reads Allow anyway: the name could be anyone’s. Allow it only if you started the connection yourself, just now, from that app.

What an assistant can see

A connection reaches one organization: the one you picked when you allowed it. In that organization the assistant can:

• list applications and devices;
• read an application’s configuration (its application YAML, as JSON);
• read deployment status, including why a deploy is stalled and which devices run the current release;
• read recent output of the application’s own workloads, from each serving device.

It can’t:

• change, restart, redeploy, create or delete anything;
• see secret values or the values of workload environment variables (they show as hidden);
• see or manage billing, members, invites, API keys or organization settings;
• reach any other organization you belong to.

Whatever your role, an assistant acts with read-only access, and never with more than your role in that organization allows. If you leave the organization or your role is lowered, its next request follows within about a minute. Read-only members can connect assistants too.

The tools behind this, for reference: whoami, list_applications, get_application, get_application_status, get_application_logs and list_devices.

Caution

Everything an assistant reads is sent to the model provider behind it, including application configuration and workload logs. Do not connect an assistant to an organization whose logs you cannot share with that provider. Never paste secret values into a chat: store them with edgible secret set and refer to them by name.

See and revoke connected apps

Account → Connected apps in the console lists every assistant you have allowed: its name (with its verified domain, if it has one), the organization it reaches, its access, and when it was connected and last used. Select one to see its recent tool calls, newest first: what it asked Edgible to do, and whether that worked or was refused.

To disconnect an assistant, select it and choose Revoke access. It is signed out at once: its next request fails. To use it again, connect it again from the assistant and allow it again.

• An assistant stays signed in while you use it. After 30 days without use it asks you to sign in again.
• After 90 days without use Edgible signs it out on its own. It stays on the list, marked Signed out: unused for 90 days, until you choose Remove.
• Removing Edgible inside the assistant doesn’t always sign it out of Edgible. To be sure, revoke it in Connected apps too.
• To work in another organization, connect again and pick that organization. Each organization you allow gets its own row.

When it doesn’t work

• The assistant sees none of your applications. It is connected to another organization. Ask it to run whoami, which names the organization. To switch, revoke it in Connected apps and connect again.
• The assistant says it can’t change anything. Hosted connections are read-only, and the assistant is told so. Make the change yourself, in the console or with the CLI, or use the local server with --allow-write.
• An organization can’t be picked on the Allow page. It is marked Suspended: no assistant can connect to it.
• The assistant can’t sign in. Check that the URL is exactly https://mcp.edgible.com/mcp. Then remove Edgible from the assistant, add it again, and allow it again.
• A tool fails with an error code. The code and message are the platform’s own; look the code up in Error codes. The request id in the message is what support needs.

On your own machine

edgible mcp runs the same tools on your machine, signed in as your CLI profile, and can also apply changes and redeploy. Use it in CI, or anywhere a browser sign-in can’t happen. A coding assistant that runs shell commands can also use the edgible CLI directly. Both are in Local server and CLI.

Related

• Host your own MCP server on Edgible
• Authentication modes
• Diagnose a broken app