Skip to content
Edgible Docs

edgible mcp

Run a local MCP server so an AI assistant can use Edgible

The server talks to the assistant over stdin and stdout and signs in as the profile you are logged into. Run it from the assistant’s configuration, not by hand. Start with read-only access; add --allow-write once you trust the setup.

Assistants that support remote MCP servers can use the hosted server instead, with nothing to install: give them https://mcp.edgible.com/mcp and sign in through the browser. Use edgible mcp where a browser sign-in can’t happen, such as CI. Setup for each assistant: https://docs.edgible.com/guides/ai-assistants/

Read tools

whoami, list_applications, get_application, get_application_status, get_application_logs, list_devices, preview_application_change

Write tools

apply_application_change, redeploy_application (only with --allow-write)

Examples

Terminal window
claude mcp add edgible -- edgible mcp
claude mcp add edgible -- edgible mcp --allow-write
claude mcp add edgible -- edgible --profile work mcp

Other assistants take a command and arguments in their configuration file: { command: edgible, args: [mcp] }

A change to an application is previewed first, and a disruptive change is not applied until the assistant passes confirm. Workload environment values are hidden from every tool.