Connect an MCP client
EdgeFetch speaks the Model Context Protocol in two ways.
Local stdio (recommended for one machine)
Section titled “Local stdio (recommended for one machine)”The client starts edgefetch mcp as a child process. Nothing listens on a port.
edgefetch install-mcp # configures Claude Desktop and CursorFor any other client, add a stdio server that runs edgefetch with the argument mcp. In the
common JSON format:
{ "mcpServers": { "edgefetch": { "command": "edgefetch", "args": ["mcp"] } }}For Claude Code:
claude mcp add edgefetch -- edgefetch mcpRemote hub over HTTP
Section titled “Remote hub over HTTP”A deployed hub serves MCP at https://<your-hub>/mcp, using OAuth 2.1 with PKCE or a bearer
token. Point your client at that URL. Dynamic client registration accepts loopback redirect URIs
by default. Allow other hosts with OAUTH_REDIRECT_ALLOWLIST.
Container
Section titled “Container”The worker image can also run the stdio server:
docker run -i --rm ghcr.io/bartrumb/edgefetch-agent:2.5.2 mcpSee the tools reference for what your agent can call.