GClimb

    Connect another MCP client

    An MCP client that connects over HTTP from an app or a server can connect to GClimb. A client running in a browser must come from an allowed origin (gclimb.io, claude.ai, claude.com): other origins are refused.

    Server address

    https://gclimb.io/api/mcp/server.php

    Transport

    • MCP over Streamable HTTP, stateless: one POST request per JSON-RPC message, JSON response.
    • Protocol versions served: 2025-11-25, 2025-06-18, 2025-03-26.

    OAuth sign-in

    For clients that handle OAuth 2.1 (dynamic client registration, PKCE). Metadata is published at https://gclimb.io/.well-known/oauth-protected-resource and https://gclimb.io/.well-known/oauth-authorization-server. The user approves access on a GClimb page.

    Access key

    Create a key on the “MCP GClimb” page of the dashboard, then send it in the header of every request:

    Authorization: Bearer YOUR_KEY

    Tools

    tools/list returns the tools open to your account, with their input schema and credit cost. All are read-only.