Connect another client

Any client that supports remote MCP servers over Streamable HTTP, with OAuth sign-in, can connect to Edgible. Give it the server URL; it signs you in through your browser the first time.

https://mcp.edgible.com/mcp

Most clients read a block like this, in a file whose name and location depend on the client:

{
  "mcpServers": {
    "edgible": { "type": "http", "url": "https://mcp.edgible.com/mcp" }
  }
}

A few command-line clients

OpenAI Codex CLI:

codex mcp add edgible --url https://mcp.edgible.com/mcp
codex mcp login edgible

Gemini CLI:

gemini mcp add --transport http edgible https://mcp.edgible.com/mcp

Then run /mcp auth edgible inside Gemini CLI to sign in.

Clients that only run local servers

A client that can start a command but can’t reach a remote server can use mcp-remote, which runs on your machine and passes everything to the hosted server. It needs Node.js.

{
  "mcpServers": {
    "edgible": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.edgible.com/mcp"] }
  }
}

mcp-remote opens your browser to sign in, and keeps the sign-in in ~/.mcp-auth.

Or run Edgible’s own local server, edgible mcp, which signs in through the CLI instead: see Local server and CLI.

The Allow page

A client that registers itself with Edgible is shown with the name it gave, and the page says Edgible can’t verify this app. Allow it only if you started the connection yourself, just now, from that client. See Apps Edgible can’t verify.

For client developers

What the hosted server expects, for anyone building or debugging a client:

Endpoint	POST https://mcp.edgible.com/mcp, Streamable HTTP, stateless: JSON responses, no Mcp-Session-Id, no SSE stream. GET and DELETE answer 405.
Protocol versions	2025-06-18, 2025-11-25 and 2026-07-28. Clients of earlier revisions fail at sign-in.
Discovery	A request without a valid token gets 401 with WWW-Authenticate: Bearer resource_metadata="https://mcp.edgible.com/.well-known/oauth-protected-resource/mcp", scope="edgible:read".
Authorization server	https://auth.edgible.com, metadata at /.well-known/oauth-authorization-server. OAuth 2.1 authorization code with PKCE (S256 only). A resource parameter, if sent, must be https://mcp.edgible.com/mcp.
Client registration	Client ID Metadata Documents (an https client_id) or Dynamic Client Registration at /register.
Redirect URIs	https, loopback http on any port, or a private-use scheme for native apps.
Scopes	edgible:read.
Tokens	Opaque bearer tokens in the Authorization header only, never in the query string. Access tokens last 1 hour; refresh tokens rotate on every use and last 30 days. A refresh token used again more than 30 seconds after its rotation revokes every token issued with it.
Revocation	RFC 7009 at /revoke. Revoking a refresh token signs the connection out.
Origin	Optional. When present it must be https, or http://localhost; anything else gets 403.

Tool failures come back as tool results with isError set, carrying the platform’s error code, message and request id.