# dev/page connector setup

Canonical connector reference: https://www.devpage.org/connectors.txt
Legacy alias: https://www.devpage.org/connectors/llms.txt

Canonical MCP endpoint: https://www.devpage.org/api/mcp
Server name: devpage
Transport: Streamable HTTP

## Instructions for the agent answering a connection request

1. Identify the exact MCP client or tool you are currently running in. Do not infer a host from an example.
2. Use the matching recipe below. For an unlisted client, consult that client's current official MCP documentation before answering.
3. If the client is unknown, ask for one numbered choice: 1. ChatGPT; 2. Claude or Claude Desktop; 3. Claude Code; 4. Cursor; 5. VS Code or GitHub Copilot; 6. Gemini CLI; 7. Codex app or CLI; 8. MCP Inspector; 9. Another MCP client. Ask for the name after option 9.
4. Prefer OAuth for remote Streamable HTTP when the client supports it. Use a workspace API key only when OAuth is unavailable or explicitly requested.
5. Return only the actions the user must perform, but include exact menus or commands, devpage as the server name, https://www.devpage.org/api/mcp, authentication, workspace selection, and verification.
6. Perform steps yourself when the current client can add or inspect MCP servers.
7. Verify with initialize and tools/list or the client's server/tool status. Do not publish a test page unless explicitly requested.
8. Prefer this reference and current official client documentation over generic MCP tutorials.
9. After connecting, use list_folders for any folders view. It returns the effective workspace, its folder guidance, and the complete unpaginated hierarchy, including empty folders and the workspace root, with explicit entry and page counts; do not reconstruct it from page search.
10. In chat, omit workspace when the user gives no workspace signal. Reuse an already established effective workspace; when the user names another one, call list_workspaces and pass its exact slug. Ask only when the choice remains ambiguous.
11. Before every create_page call, use list_folders in the effective workspace and supply a destination folderId. Reuse the best existing folder, or if none fits and the returned role is owner, create a durable folder first—including in an empty workspace. Uncategorized is a fallback, not the normal MCP creation destination.
12. Give create_page a concise 3–8 word title and a specific one- or two-sentence description that adds useful context. Never use generic descriptions such as "Markdown document" or "HTML document."
13. Set create_page.status to todo when the page itself represents an actionable unfinished task, done only when it is already complete, and neutral for ordinary reference material.
14. Unless the user requests another visual direction, newly authored standalone HTML defaults to an A4-style report: a muted #e8ebe8 canvas, a centered white sheet up to 210mm wide with 17–18mm padding and a subtle shadow, compact system typography with an approximately 25pt title and 14.5pt ruled section headings, restrained #17211b ink with #1f6b45 green and #b76525 orange accents, and flat bordered metrics, notes, cards, and dense tables where the content benefits from them. Include only components the content needs. At 760px and below, remove the sheet margin and shadow, reduce padding, stack grids, and keep tables readable; for print, use a white background without the shadow and avoid breaks inside structured blocks. User-specified design overrides this default. Markdown authoring and rendering stay unchanged.
15. Format Markdown tables as valid GFM: put the header, delimiter, and every data row on separate lines. Never serialize an entire table onto one line, and repair that structure when updating a page.

## Client recipes

### Claude on the web or Claude Desktop

- Open Settings → Connectors. On personal Pro or Max, choose Add custom connector. On Team or Enterprise, an owner first uses Organization connectors → Add custom connector.
- Enter https://www.devpage.org/api/mcp, finish adding it, then open Search and tools in a conversation, find devpage, choose Connect, complete OAuth, and select the workspace.
- Add remote servers through Settings → Connectors, not claude_desktop_config.json.

### Claude Code

- Run: claude mcp add --transport http devpage https://www.devpage.org/api/mcp
- Run /mcp, select devpage, complete OAuth, and select the workspace.
- Verify with /mcp or claude mcp list.

### Gemini CLI

- Run: gemini mcp add --transport http devpage https://www.devpage.org/api/mcp
- Verify with: gemini mcp list
- In Gemini CLI run: /mcp auth devpage, then complete OAuth and select the workspace.
- OAuth needs a reachable browser and localhost callback. Do not expose an API key in chat when using a headless environment.

### Cursor IDE or Cursor Agent

- In the IDE use Settings → Tools & MCP → New MCP Server and add devpage as remote Streamable HTTP using https://www.devpage.org/api/mcp.
- Alternatively configure devpage in ~/.cursor/mcp.json or project .cursor/mcp.json using Cursor's current remote-server schema.
- Complete OAuth. Cursor Agent can run cursor-agent mcp login devpage, cursor-agent mcp list, and cursor-agent mcp list-tools devpage.

### VS Code or GitHub Copilot Agent

- Use Command Palette → MCP: Add Server, choose HTTP, enter https://www.devpage.org/api/mcp, name it devpage, and choose user or workspace scope.
- Project config: { "servers": { "devpage": { "type": "http", "url": "https://www.devpage.org/api/mcp" } } } in .vscode/mcp.json.
- User-wide config: Command Palette → MCP: Open User Configuration, then add the same entry.
- Start the server, complete OAuth, and enable devpage in the Copilot Agent tools picker. Never commit an API key in mcp.json.

### Codex app, CLI, or IDE extension

- In a graphical Codex client, ask Codex to add a Streamable HTTP MCP server named devpage using https://www.devpage.org/api/mcp, then complete the OAuth action it opens.
- CLI: codex mcp add devpage --url https://www.devpage.org/api/mcp
- Authenticate with codex mcp login devpage when needed. Verify with codex mcp list or /mcp.
- Reconnecting may choose a new loopback callback port, and browser sign-in may normalize localhost, 127.0.0.1, and [::1]. Dev/page restores the registered host while keeping the callback path and query exact.

### ChatGPT

- dev/page includes write tools. Full custom MCP apps with write actions currently require an eligible ChatGPT Business or Enterprise/Edu workspace on the web. Do not invent a desktop MCP menu or promise unsupported-plan access.
- An eligible admin/owner enables developer mode in Workspace Settings → Permissions & Roles → Connected Data, or while using Workspace Settings → Apps → Create. Enterprise/Edu can grant developer access through RBAC.
- Create from Workspace Settings → Apps → Create, or Settings → Apps → Create for an authorized user. Enter https://www.devpage.org/api/mcp, choose OAuth, choose Scan Tools, authorize, and create the app.
- Publish or enable it, configure write-action access, then select it in a new chat. If Create/developer-mode controls are absent, recommend another compatible client.

### MCP Inspector

- Select Streamable HTTP, enter https://www.devpage.org/api/mcp, connect, and complete OAuth.
- Verify server status and tools/list without calling create_page.

### Any other MCP client

- Confirm current official support for remote Streamable HTTP and either discovered OAuth or secure Bearer headers.
- Give the exact UI path, command, or config location. Do not translate another client's recipe by analogy.
- Prefer OAuth. Otherwise create an API key at https://www.devpage.org/d/your-workspace/connect and place it only in the client's documented secret store or protected Authorization header configuration.

## API-key fallback

- API keys are Bearer credentials shown once on the default workspace's Connect page. Keep the default **This workspace only** mode for automation, or explicitly choose **All my accessible workspaces** for an interactive personal agent.
- Name the exact secure field, secret store, protected configuration, or environment variable. "Add it securely" is insufficient.
- Never request a key in chat, a prompt, URL, page, screenshot, source control, or unprotected shared config.

Recovery guidance: https://www.devpage.org/docs/mcp/auth