Beta
Cursor
Cursor mcp.json remote server with the Bearer header interpolated from the environment.
| Family | xAI |
|---|---|
| Auth method | pat_swap |
| Origin | local |
| Token step | PAT swap: export the JWT before launching Cursor; mcp.json interpolates it with ${env:}. OAuth later. |
| Status | Available |
| Version | — |
| Released | — |
| 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 |
Steps
- Get a PAT. Ask your operator for an AWP PAT, then exchange it at the token endpoint for a Bearer JWT. Save it to
~/.config/awp/edge.patwith mode 600. Never paste it into chat or commit it. - Install the token script. Save as
~/.config/awp/awp-edge-token.sh(chmod 700). It prints a Bearer JWT valid for 15 minutes. - Configure Cursor. Add the config below.
- Load the token. Cursor reads ${env:AWP_EDGE_JWT} from the environment it was launched from. Re-export and relaunch after 15 minutes.
- Get your twin connected. Paste the prompts below into the agent, in order.
1. Token script
~/.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": "..."
}
2. Configure Cursor
Cursor MCP config
~/.cursor/mcp.json
{
"mcpServers": {
"awp-edge": {
"url": "https://edge.a24labs.net/mcp",
"headers": { "Authorization": "Bearer ${env:AWP_EDGE_JWT}" }
}
}
}Start Cursor with a fresh token
shell
export AWP_EDGE_JWT="$(~/.config/awp/awp-edge-token.sh)"
cursor.
3. Load the token
Cursor reads ${env:AWP_EDGE_JWT} from the environment it was launched from. Re-export and relaunch after 15 minutes.
4. Get your twin connected
Your PAT is bound to a twin workspace; these prompts confirm the connection end to end.
- List the tools the awp-edge MCP server exposes.Expect: 5 tools on this Edge (fewer if your PAT lacks a capability).
- Call the awp-edge tool discovery with limit 5 and list the resource ids it returns.Expect: Up to five resources labelled STORE (evidence.source=awp-store).
- Call workspace_search with query "agents hub" and limit 5.Expect: Up to five STORE results.
- Call project_query with {"id": "<project-id>"}. Use id only; free-text query is unsupported.Expect: One project, or a clear bad-args error if you pass query.
OAuth sign-in (optional)
For clients that support OAuth sign-in instead of a static header. Authorization server https://id.a24labs.net/realms/a24labs, public client awp-edge-mcp-oauth, PKCE S256.
Machine-readable: /recipes/cursor/recipe.json · /llms.txt · /recipes.json · /catalog.json · No-script start page: /start/