not yet available
Claude Desktop
Remote MCP connector with OAuth sign-in bound to a PAT record. An interim local bridge (unverified) is on the page.
| Family | Anthropic |
|---|---|
| Auth method | oauth |
| Origin | vendor_cloud |
| Token step | OAuth sign-in bound to a PAT record: Front Door issues a JWT with the same claims as the PAT exchange. |
| Status | Not yet available on PROD. |
| Version | — |
| Released | — |
Not yet available on PROD. The flow below is planned; it does not work yet.
Planned flow
- Add
https://edge.a24labs.net/mcpas a remote MCP connector in Claude Desktop. - Claude follows the
401challenge to the Protected Resource Metadata and the authorization server. - You sign in through Front Door (authorization code + PKCE) and pick the PAT record the connection is bound to.
- Front Door issues a JWT with the same claims as the PAT exchange: one twin workspace, its capabilities, no org_admin. Revoking the PAT ends access.
Interim: local mcp-remote bridge
A local workaround, not this card's flow: Claude Desktop starts mcp-remote on your machine, which carries a PAT-swap JWT to Edge. It uses the PAT exchange, so it works before OAuth sign-in is available. Beta until EEG, like the other Beta cards.
| 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 |
~/.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"])'
Desktop config
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"awp-edge": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://edge.a24labs.net/mcp", "--header", "Authorization:${AWP_EDGE_AUTH}"],
"env": { "AWP_EDGE_AUTH": "Bearer <JWT from awp-edge-token.sh>" }
}
}
}
Paste a fresh JWT into AWP_EDGE_AUTH and restart Claude Desktop. The JWT lasts 15 minutes, so this suits short sessions; Claude Code's headers helper is the better fit for long ones.
Once connected: get your twin connected
- 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.
Machine-readable: /recipes/claude-desktop/recipe.json · /llms.txt · /recipes.json · /catalog.json · No-script start page: /start/