not yet available

ChatGPT

Remote MCP connector from ChatGPT's cloud with OAuth sign-in bound to a PAT record.

FamilyOpenAI
Auth methodoauth
Originvendor_cloud
Token stepOAuth sign-in bound to a PAT record: Front Door issues a JWT with the same claims as the PAT exchange.
StatusNot yet available on PROD.
Version—
Released—
Not yet available on PROD. The flow below is planned; it does not work yet.

Planned flow

  1. Add https://edge.a24labs.net/mcp as a remote MCP connector in ChatGPT.
  2. ChatGPT follows the 401 challenge to the Protected Resource Metadata and the authorization server.
  3. You sign in through Front Door (authorization code + PKCE) and pick the PAT record the connection is bound to.
  4. 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.

Once connected: get your twin connected

  1. List the tools the awp-edge MCP server exposes.
    Expect: 5 tools on this Edge (fewer if your PAT lacks a capability).
  2. 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).
  3. Call workspace_search with query "agents hub" and limit 5.
    Expect: Up to five STORE results.
  4. 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/chatgpt/recipe.json · /llms.txt · /recipes.json · /catalog.json · No-script start page: /start/