Cursor

Publish, list and seal pagelets from Cursor's agent.

Cursor's mcp.json takes a remote URL plus headers — full Pagelet tool access in chat and agents.

Configure

Register a token first (one curl call). Cursor reads MCP servers from~/.cursor/mcp.json (global) or .cursor/mcp.json in a project. Use the${env:…} interpolation so the token stays in your shell environment, not the file:

~/.cursor/mcp.json

{
  "mcpServers": {
    "pagelet": {
      "url": "https://pagelet.link/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PAGELET_TOKEN}"
      }
    }
  }
}

A remote entry with url speaks streamable HTTP automatically — no type field needed. Don't check a project-scoped file with a literal token into version control.

Verify it works

Open Customize in the sidebar — pagelet appears under MCP servers; toggle it on.
In chat, ask "what pagelet tools are available?" — the agent lists them from the server.
Tool calls ask for approval by default; expand the arrow to inspect arguments before allowing.

First pagelet

Ask: "Make a pagelet onboarding guide for this repo and publish it." Cursor callspublish_pagelet and returns a https://<slug>.usepagelet.com URL. Open it — that's success.

Troubleshooting

"Auth required" tool errors — PAGELET_TOKEN isn't in Cursor's environment. Export it in your shell profile and fully restart Cursor (it inherits env at launch).
Server shows an error or no tools — open the Output panel (Cmd/Ctrl+Shift+U) → MCP Logs for the connection error.
Empty tool list — check the URL is exactly https://pagelet.link/mcp and /api/capabilities shows service.mcp: true.
Edits not picked up — toggle the server off/on in Customize, or restart Cursor.

Source: Cursor MCP docs (remote server shape and interpolation verified there).