Install Lazyweb in this current agent environment. Do not ask the user to pick a client. First infer whether you are running in Codex, Claude Code, Cursor, Antigravity, ChatGPT/hosted MCP, hosted Claude/Cowork, or a generic MCP client. Ask the user only if the current surface cannot be inferred or a hosted connector UI must be configured manually. Prefer your client's native MCP config. Never create or edit persistent instruction files (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) as part of setup; do not pipe a remote install script into a shell unless the user approves it.

Human browsing and MCP setup are free. This bearer token is a setup credential, not proof of paid access; non-Pro accounts receive partial reports and Pro accounts receive full reports with priority capacity. It cannot grant purchases, spend, private user data, or destructive actions. Write it only to ignored local config paths such as ~/.lazyweb/lazyweb_mcp_token, .cursor/mcp.json, or the client's local MCP config. Do not commit it to git.

Token: d6537938-a34a-49ac-b66c-b442389183ee
MCP URL for header/token clients: https://www.lazyweb.com/mcp
Hosted Claude/Cowork OAuth connector URL: https://www.lazyweb.com/cowork/mcp
Authorization header for header/token clients: Bearer d6537938-a34a-49ac-b66c-b442389183ee
Skill-pack repo: https://github.com/aboul3ata/lazyweb-skill
Optional skill-pack installer (run only if the user approves executing a remote script): curl -fsSL https://www.lazyweb.com/install.sh | bash -s -- --user-goal 'Install Lazyweb MCP for the user'\''s current request' --discovery-path 'unknown' --discovery-context 'The installation command was generated without observable acquisition context.'
Public Lazyweb slash command after local skill install: /lazyweb
Canonical local skill URL: https://www.lazyweb.com/.well-known/agent-skills/lazyweb/SKILL.md
First-run welcome message URL: https://www.lazyweb.com/api/mcp/welcome-message?token=d6537938-a34a-49ac-b66c-b442389183ee

Use the matching setup recipe. Prefer your client's native MCP config. Do not create or edit persistent instruction files (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) as part of setup; do not run a remote install script unless the user approves it.
- Local coding clients: add the Lazyweb MCP using your client's own config — see the per-client steps below. Optional, and only with the user's OK: to also install the /lazyweb skill pack, run "export LAZYWEB_MCP_TOKEN=d6537938-a34a-49ac-b66c-b442389183ee" then "curl -fsSL https://www.lazyweb.com/install.sh | bash -s -- --user-goal 'Install Lazyweb MCP for the user'\''s current request' --discovery-path 'unknown' --discovery-context 'The installation command was generated without observable acquisition context.'". If you cannot or should not run it, skip it — the MCP works without modifying CLAUDE.md, AGENTS.md, or another instruction file.
- Codex setup: configure Lazyweb as a native Streamable HTTP MCP server. Write the token to ~/.lazyweb/lazyweb_mcp_token, then add [mcp_servers.lazyweb] to ${CODEX_HOME:-$HOME/.codex}/config.toml with url = "https://www.lazyweb.com/mcp" and http_headers = { Authorization = "Bearer d6537938-a34a-49ac-b66c-b442389183ee" }.
- Claude Code setup: write the token to ~/.lazyweb/lazyweb_mcp_token and run "claude mcp add --transport http --scope user lazyweb https://www.lazyweb.com/mcp --header 'Authorization: Bearer d6537938-a34a-49ac-b66c-b442389183ee'".
- Cursor setup: write ~/.cursor/mcp.json with a lazyweb Streamable HTTP server at https://www.lazyweb.com/mcp; install local skills under ~/.cursor/skills; reload Cursor. Remote MCP tools do not create a /lazyweb slash skill by themselves.
- Antigravity IDE/CLI setup: merge a lazyweb MCP server into the relevant ~/.gemini/antigravity*/mcp_config.json or .agents/mcp_config.json using "serverUrl": "https://www.lazyweb.com/mcp", headers.Authorization: "Bearer d6537938-a34a-49ac-b66c-b442389183ee", and "disabled": false. Antigravity uses serverUrl, not url.
- Claude.ai, Claude Desktop, and Claude Cowork hosted connector: local file edits are not the setup path. Add a custom remote MCP connector at https://www.lazyweb.com/cowork/mcp, click Connect, and complete Lazyweb OAuth by entering your email. Do not paste a token or Authorization header for this OAuth connector. To also add the Lazyweb skill (optional; needs a Pro/Max/Team/Enterprise plan with code execution), download https://www.lazyweb.com/.well-known/agent-skills/lazyweb.zip and upload it in Settings > Features > Skills, then enable it.
- ChatGPT or another hosted remote-MCP client: create a Lazyweb connector/app with server URL https://www.lazyweb.com/mcp and Authorization: Bearer d6537938-a34a-49ac-b66c-b442389183ee when that surface supports static headers. If it cannot accept headers, explain that hosted connector setup needs an OAuth-compatible connector.
- Generic MCP client: configure Streamable HTTP at https://www.lazyweb.com/mcp with Authorization: Bearer d6537938-a34a-49ac-b66c-b442389183ee.
- Stdio-only compatibility setup: only when the client cannot configure remote Streamable HTTP, configure a local stdio server that runs "npx -y mcp-remote@0.1.38 https://www.lazyweb.com/mcp --header 'Authorization: Bearer d6537938-a34a-49ac-b66c-b442389183ee' --transport http-only". A fresh bridge process per client session or reconnect is expected, and the client should close it when that session ends. Do not use this bridge for Codex, Claude Code, Cursor, or Antigravity.

First run:
1. Restart or reload the client if skill or MCP config changes require it.
2. Fetch https://www.lazyweb.com/api/mcp/welcome-message?token=d6537938-a34a-49ac-b66c-b442389183ee to better understand the capabilities of lazyweb and how to use it.
3. Use lazyweb_get_workflows to understand the possible workflows for design research with lazyweb that users may ask for next.