Skip to main content
Your client must support remote MCP over Streamable HTTP. Clients that only start local MCP processes cannot connect to this URL directly.
1

Add the remote server

Open your client’s MCP settings, add an HTTP server named glasser, and use this URL:
2

Connect your account

If the client supports OAuth with automatic client registration, choose OAuth and follow the sign-in prompt. Sign in to Glasser, choose your Workspace, and select Allow. Create an account and Workspace if needed.If the client requires a fixed credential, use the Key setup below instead.
3

Check the connection

In a new conversation, ask:
The agent should use Glasser’s balance tool and return your balance. This check is free; a zero balance still means the connection works. If you need funds for a paid Run, add them in the Glasser console.

​
Try your first request

After you approve, the agent can retrieve the data and report the result and charge.

​
Connect with a Key

  1. Create a Key on the Glasser Keys page. Its value is shown once.
  2. Make the value available as GLASSER_API_KEY in the environment that starts your client.
  3. Configure the server URL and an Authorization header with the value Bearer <your Key>. Use your client’s environment-variable syntax, as in the examples below, instead of saving the Key in the configuration file.
  4. Restart or reconnect the client and repeat the free balance check.
Merge the relevant entry into your existing configuration. The examples use different formats because each client has its own settings.
If the client still cannot connect, check that it can read GLASSER_API_KEY and supports Streamable HTTP. Revoke and replace a lost Key on the Keys page. For each client’s configuration syntax, see the official guides for Claude Code, Codex, Cursor, and OpenCode.