Connect with an API Key
For an agent that can't sign you in, create an API Key and give it to the agent.
On this page
Add the server #
For an agent that can't sign you in, create an API Key. The agent sends it in this header on every request:
Authorization: Bearer <your API Key> Many clients take a settings file like this one. Some leave out type:
{
"mcpServers": {
"glass-page-key": {
"type": "http",
"url": "https://mcp.glasspage.ai/mcp",
"headers": {
"Authorization": "Bearer <your API Key>"
}
}
}
} Or add it to Claude Code with a key, under its own name, glass-page-key, apart
from the sign-in setup:
claude mcp add --transport http --scope user glass-page-key https://mcp.glasspage.ai/mcp --header "Authorization: Bearer <your API Key>" Or, for Codex, which reads the key from an environment variable, under that same name:
codex mcp add glass-page-key --url https://mcp.glasspage.ai/mcp --bearer-token-env-var GLASS_PAGE_API_KEY On macOS and Linux, put your key in a file of its own, such as ~/.config/glass-page.env,
never in a project, and never commit it:
export GLASS_PAGE_API_KEY="<your API Key>" Then load it in your shell's profile, such as ~/.zshrc or ~/.bashrc:
[ -f ~/.config/glass-page.env ] && . ~/.config/glass-page.env On Windows, set it for your account in PowerShell:
setx GLASS_PAGE_API_KEY "<your API Key>" GLASS_PAGE_API_KEY reaches only Codex started from a terminal opened after you set it. The
ChatGPT desktop app and the IDE extension may not see it, so sign them in with OAuth instead, as
Codex's steps show.
Check it works #
Ask your agent which Workspaces it can see. It lists them, and publishes nothing.
Which Glass Page Workspaces can you see?
It lists your Workspaces, and publishes nothing. If it can't, or asks you to sign in, it isn't connected yet.
If it doesn't connect #
- Requests are refused. The key was revoked, or mistyped. Create a new one in Connections.
More in Troubleshooting.
You see a key only once. Never paste it into a chat, a Pane, or a file a project commits.