Pagelet/ docs
Get started
Docs menu

ChatGPT

Connect ChatGPT to Pagelet via a developer-mode MCP app — with one honest limitation.

ChatGPT discovers Pagelet tools via a developer-mode connector — but it can't send the bearer token, so publishing is read-only here.

The limitation, up front

ChatGPT's custom MCP apps authenticate with OAuth, no authentication, or mixed — there is no field for a static Authorization header, and Pagelet uses bearer tokens, not OAuth. So a ChatGPT connector reaches only the open tools: tool discovery and get_capabilities. Anything that publishes or reads your artifacts answers "Auth required". If ChatGPT adds bearer/static-key auth to connectors later, this page will be updated — check the source links below.

Configure the connector

  1. In ChatGPT (web), open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins, click + and create a developer-mode app.
  3. Set the MCP server URL to https://pagelet.link/mcp (streaming HTTP) and authentication to None.
  4. Save — the app appears under Settings → Apps with a Dev label.

Full MCP (write actions) in developer mode is available on Pro, Plus, Business, Enterprise and Edu web accounts. On Business/Enterprise/Edu workspaces an admin publishes the app before members can use it.

Verify it works

  • Open a chat, choose Developer mode from the + menu and enable your Pagelet app.
  • Ask: "Use the Pagelet app's get_capabilities tool." You get the live service manifest back.
  • Tool calls are inspectable — expand a call to see the exact JSON in and out.

Actually publishing

ChatGPT can still author a pagelet (the HTML with the runtime tag — point it atllms.txt for the contract). Publish the result from something that can set headers: the Codex CLI shares your ChatGPT account and has full bearer support, or one curl from any terminal:

publish via REST
curl -sS -X POST https://pagelet.link/api/upload \
  -H 'content-type: application/json' \
  -H 'authorization: Bearer pgl_…' \
  -d '{"html":"<!doctype html>…","title":"…"}'

Troubleshooting

  • App shows no tools — the server scans on create; use Refresh in the app's settings page to re-pull the tool list.
  • "Auth required" on publish — expected; see the limitation above. It's not a misconfiguration.
  • Write actions keep asking — that's ChatGPT's confirmation gate for non-read-only tools; approve per call or remember the choice for the conversation.
  • Connector won't connect at all — ChatGPT connects from OpenAI's cloud; the server must be publicly reachable. /api/capabilities confirms Pagelet's side is up.

Sources: ChatGPT developer mode andDeveloper mode and MCP apps in ChatGPT (auth options verified there).