Skip to content
Load Factor Docs
Open Load Factor

Article

Other MCP clients

What an MCP client needs to connect to Load Factor (Streamable HTTP and OAuth 2.1 with PKCE), and how to check the server from the command line.

  • MCP
  • Updated

Overview

Any MCP client that supports the Streamable HTTP transport and OAuth sign-in can connect to Load Factor, not only Claude and ChatGPT. This page lists what the server expects, which sign-in redirects it accepts, and how to check it from the command line.

Connection

Endpoint https://mcp.loadfactorenergy.com/mcp
Transport Streamable HTTP. The server answers with JSON responses and keeps no session between requests.
Authorization OAuth 2.1 authorization code flow with PKCE (S256), as the MCP authorization spec describes
Identity Google sign-in. The Google account's verified email address must belong to a Load Factor user with MCP access.
Note:

The MCP endpoint keeps its current address, mcp.loadfactorenergy.com, for now; we'll announce any change in the changelog.

Authorization details

The server publishes its OAuth metadata, so a client that follows the MCP authorization spec discovers everything on its own:

  • Protected resource metadata (RFC 9728): https://mcp.loadfactorenergy.com/.well-known/oauth-protected-resource/mcp. An unauthenticated request to the endpoint gets HTTP 401 with a WWW-Authenticate header that points here.
  • Authorization server metadata: https://mcp.loadfactorenergy.com/.well-known/oauth-authorization-server.
  • Client registration: a Client ID Metadata Document (an https client id), or Dynamic Client Registration (RFC 7591). Public clients that use PKCE need no client secret.
  • Registration rules: grant types authorization_code and refresh_token only, response type code, at most 10 redirect URIs of up to 512 characters, and a client name of up to 120 printable characters.
  • Scopes: ask for openid email. profile and offline_access are accepted too, but the grant is always openid plus your email address; any other scope is refused with invalid_scope.
  • Tokens: access tokens are short-lived and come with a refresh token. Use the refresh token rather than signing the user in again.

Accepted redirect URIs

A client can register only redirect URIs on this list, and must then use one it registered.

Client Redirect URI
Claude (web, desktop, mobile) https://claude.ai/api/mcp/auth_callback, https://claude.com/api/mcp/auth_callback
ChatGPT https://chatgpt.com/connector_platform_oauth_redirect, https://chatgpt.com/connector/oauth/…
Local clients (Claude Code, desktop tools, scripts) http://localhost:<any port>/…, http://127.0.0.1:<any port>/…

A local client may listen on a different port each time it signs in; the path must stay the one it registered.

Note:

Building a client that runs on another host? Contact us with its redirect URI and we can add it.

Check the server from the command line

The discovery documents are public, so you can confirm the server is reachable before you connect a client:

Terminal
curl https://mcp.loadfactorenergy.com/.well-known/oauth-protected-resource/mcp

The answer names the resource (https://mcp.loadfactorenergy.com/mcp) and the authorization server. Tool calls need a signed-in token, so there is nothing more to see without one.

Browser-based clients

Tools that run inside a web page, such as MCP Inspector (http://localhost:6274), call the server from that page. The server only accepts browser requests from web origins it knows, so these tools get 403 Forbidden Origin. Desktop, command-line and hosted clients are not affected. If you need a browser-based client allowed, contact us with its origin.

After you connect

Call whoami first: it shows the access the server applies to you. The full list of tools, resources and prompts is in MCP tools.