Agent Hub
Onboarding for agents connecting to the AWP Edge MCP server in production. Everything on this site is public; tool calls need a token. This hub is not the MCP endpoint: Edge is.
Browser-only agent, or a fetcher that blocks scripts or JSON? Use the no-script start page: the same discovery and every card's token step as plain HTML.
| Environment | production |
|---|---|
| MCP endpoint | https://edge.a24labs.net/mcp |
| Token endpoint (PAT exchange) | https://frontdoor.a24labs.net/v1/oauth/token |
| Auth | Front Door PAT exchange → Bearer JWT (15 min); or OAuth PKCE, client awp-edge-mcp-oauth |
Connect in three steps
- Get a PAT. Ask your operator for an AWP PAT, then exchange it at the token endpoint for a Bearer JWT. Keep it in a mode-600 file; never paste it into chat.
- Exchange it for a JWT. Front Door PAT exchange, or OAuth sign-in with the public PKCE client
awp-edge-mcp-oauth. The JWT lasts 15 minutes.~/.config/awp/awp-edge-token.sh#!/bin/bash # awp-edge-token.sh — exchange an AWP PAT for a 15-minute Edge JWT. Prints the JWT only. # The PAT is read from a mode-600 file and sent on stdin, so it never appears in argv or history. set -euo pipefail PAT_FILE="${AWP_PAT_FILE:-$HOME/.config/awp/edge.pat}" printf '{"grant_type":"urn:awp:params:oauth:grant-type:pat","secret":"%s"}' "$(cat "$PAT_FILE")" | curl -sS --fail-with-body -X POST "https://frontdoor.a24labs.net/v1/oauth/token" \ -H 'content-type: application/json' --data-binary @- | python3 -c 'import json,sys; print(json.load(sys.stdin)["access_token"])'Token endpoint response{ "access_token": "<JWT>", "token_type": "Bearer", "expires_in": 900, "scope": "..." } - Configure your client with
Authorization: Bearer <JWT>againsthttps://edge.a24labs.net/mcp. Pick your runtime's card; cards are grouped by product family.
xAI
GrokBot
Verified seed: add Edge as a remote MCP server with a Bearer JWT; first client proven end to end.
BetaCursor
Cursor mcp.json remote server with the Bearer header interpolated from the environment.
Anthropic
Claude Code
Remote HTTP MCP server in.mcp.json; a headersHelper script fetches a fresh JWT on every connect.
not yet availableClaude Desktop
Remote MCP connector with OAuth sign-in bound to a PAT record. An interim local bridge (unverified) is on the page.
OpenAI
ChatGPT
Remote MCP connector from ChatGPT's cloud with OAuth sign-in bound to a PAT record.
BetaCodex CLI
Codex CLI streamable-HTTP MCP server; an http_headers_helper script fetches a fresh JWT.
Gemini CLI
Gemini CLI settings.json HTTP MCP server with the Bearer header taken from the environment.
not yet availableAI Studio
Remote MCP from Google AI Studio's cloud with OAuth sign-in bound to a PAT record.
AWP
awp CLI
AWP's own command-line client, with the PAT exchange built in.
not yet availableAWP Desktop
AWP's desktop client (based on Rakazo, Apache-2.0): paste your edge-mcp PAT once, swaps it for a JWT, and reaches Edge over Path #1. Full mode runs the Rakazo stack with an AWP EEG connector; thin "AWP twins" mode talks to twin_* / ih_* with no Docker.
Discovery for agents
Standard MCP clients start at the MCP endpoint and follow the 401 challenge. Every document below is public.
- MCP endpoint —
https://edge.a24labs.net/mcp
POST without a token returns401withWWW-Authenticate: Bearer resource_metadata="https://edge.a24labs.net/.well-known/oauth-protected-resource"(MCP authorization spec). - Protected Resource Metadata —
https://edge.a24labs.net/.well-known/oauth-protected-resource
RFC 9728: the MCP resource and its authorization server. - Authorization server metadata —
https://id.a24labs.net/realms/a24labs/.well-known/openid-configuration
Issuer, token and JWKS endpoints. - AWP auth discovery —
https://edge.a24labs.net/discovery/v1/authentication
The PAT exchange (mint) block: token endpoint, grant type, required claims. - Edge bootstrap —
https://edge.a24labs.net/.well-known/awp-eeg
Gateway identity and links.
Machine-readable: /index.json · /llms.txt · /recipes.json · /catalog.json · No-script start page: /start/