Documentation Index
Fetch the complete documentation index at: https://docs.edge.glitchexecutor.com/llms.txt
Use this file to discover all available pages before exploring further.
The MCP server is on the roadmap, not yet shipped. This page is a
forward-looking spec — what it’ll look like when it lands.
What it’ll be
A small streamable-HTTP MCP server athttps://mcp.edge.glitchexecutor.com that
wraps every route on the public API and exposes them as MCP tools. Auth = the
same personal API key you use for the REST API.
Why
Glitch Edge is positioning around AI agents managing strategies. MCP closes the loop: instead of telling Claude “go write a Python script that calls these endpoints to monitor my account,” you tell Claude “use my Glitch Edge MCP” — and Claude has direct, typed, scoped tools.Tools (sketch)
/v1/keys CRUD as MCP tools — having an
agent able to mint or revoke its own auth credential is too sharp an edge. Key
management stays in the SPA.
Setup (when it ships)
Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json
gle_* token as the REST API. Per-user, scoped to one user’s account.