# Connect dev/page to an agent

Use the workspace name, MCP endpoint, and Connect-page URL supplied in the user's prompt.

1. Read the dev/page product guidance at https://www.devpage.org/llms.txt and the client-specific connection rules at https://www.devpage.org/connectors.txt before answering.
2. Identify the exact MCP client or tool you are running in, then determine whether it supports OAuth or needs an API key.
3. Follow the matching connectors.txt recipe and give a concise checklist for this exact client. Include the precise menu path and button names, or the exact command/config-file steps, for adding a Streamable HTTP server named "devpage", entering the supplied endpoint, selecting the supplied workspace as the stable default, reviewing workspace access, and verifying the connection without publishing a page.
4. If you can perform a step yourself, do it and list only what the user must do.
5. If you cannot identify the client, do not guess. Ask the user to reply with one option number only and show this numbered list, one option per line: 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. If the user replies 9, ask for the client name.
6. Prefer OAuth. If an API key is required, direct the user to the supplied workspace Connect-page URL and name the exact secure field, secret store, or environment variable where it belongs.
7. Prefer dev/page's connector rules and the client's current official documentation over generic MCP guidance.
8. Never ask the user to paste credentials into chat or page content.

Defaults when the prompt omits a value:
- MCP endpoint: https://www.devpage.org/api/mcp
- Connect page: https://www.devpage.org/d?section=connect