# Lazyweb Claude Setup

Lazyweb has two Claude install paths:

1. Claude Code uses the standalone Lazyweb skill pack and direct MCP config.
2. Claude.ai, Claude Desktop, and Claude Cowork use a custom remote MCP connector.

Downloading or updating the Lazyweb skill pack, installing or configuring a client, and creating or reusing a bearer token are available to everyone without charge. Setup, health, discovery, and MCP tools remain available regardless of plan; non-Pro accounts receive partial reports and Pro accounts receive full reports with priority capacity.

## Claude Code

Set Claude Code up with one transparent step — no remote install script required.

1. Connect the MCP with Claude Code's native command:

```bash
claude mcp add --transport http --scope user lazyweb https://www.lazyweb.com/mcp --header "Authorization: Bearer <token from ~/.lazyweb/lazyweb_mcp_token>"
```

Optional — install the `/lazyweb` skill pack for guided workflows. Run this only if the user is OK executing a remote script:

```bash
curl -fsSL https://www.lazyweb.com/install.sh | bash
# If the installer requests attribution, rerun with the five flags it prints using the user's real goal, discovery evidence, company (or explicit unknown), and intended outcome.
```

The skill pack installs `/lazyweb` plus the visible Lazyweb skills into `~/.claude/skills` and stores an account-bound setup token (read from `LAZYWEB_MCP_TOKEN`, then `~/.lazyweb/lazyweb_mcp_token`, then `https://www.lazyweb.com/api/mcp/install-token`). Claude Code exposes these skills when local skills are enabled:

- `/lazyweb`
- `/lazyweb-growth-score`
- `/lazyweb-growth-report`
- `/lazyweb-growth-backlog`
- `/lazyweb-search-experiments`
- `/lazyweb-search-flows`
- `/lazyweb-search-screens`
- `/lazyweb-update`

## Verify In Claude Code

1. Use `/mcp` and confirm Lazyweb is connected.
2. Confirm `/lazyweb` and the visible mode skills appear.
3. Ask Claude Code to run `lazyweb_get_workflows` with `{"operation":"list","task_context":"first run Lazyweb capabilities"}`, then summarize the returned workflows as Lazyweb's super powers.
4. Do not call `lazyweb_get_flows` for this first-run capability guide; that tool is for ordered product journeys.

## Claude.ai / Claude Desktop / Claude Mobile (OAuth connector)

Local shell installers do not configure hosted Claude surfaces. Claude.ai, Claude Desktop, and Claude Mobile connect through a remote MCP connector and authenticate it with OAuth — there is no field to paste an Authorization header. Lazyweb runs a standard OAuth 2.1 authorization server (PKCE + Dynamic Client Registration) on the `/mcp` resource, so setup is a URL plus a short email verification.

Add a custom connector named `Lazyweb`:

- Remote MCP server URL: `https://www.lazyweb.com/mcp`
- Click **Connect**. Claude discovers Lazyweb's OAuth automatically; sign in with your email and the 6-digit code Lazyweb sends you. No token, API key, or header is required — Lazyweb applies your account plan automatically.
- Enable the connector in the conversation before using Lazyweb tools.

Try these first:

1. `Find real onboarding flows from top fitness apps and pull the screens worth copying.`
2. `Search Lazyweb for pricing-page A/B tests in consumer subscription apps and summarize what actually won.`
3. `Generate a Lazyweb growth report for https://example.com and open it when it's ready.`

Existing Claude Cowork connectors on `https://www.lazyweb.com/cowork/mcp` keep working unchanged. The header-based `https://www.lazyweb.com/mcp` bearer path remains for clients that send `Authorization: Bearer <token>` (Claude Code, Cursor, Codex, Antigravity). Claude connects from Anthropic cloud infrastructure, so the connector URL must be reachable from the public internet.

## Add the Lazyweb skill (optional)

The connector above gives Claude the Lazyweb *tools*. Adding the Lazyweb *skill* also teaches Claude when and how to use them automatically. Skills upload separately on each hosted surface (claude.ai, Claude Desktop, Cowork):

1. Download the packaged skill: `https://www.lazyweb.com/.well-known/agent-skills/lazyweb.zip`
2. In Claude, open **Settings → Features**, find **Skills**, and choose **Upload skill**.
3. Select `lazyweb.zip`, then **enable** the Lazyweb skill.

Custom skills require a Pro, Max, Team, or Enterprise Claude plan with code execution enabled, and are per-user (each teammate uploads their own). The skill guides Lazyweb usage; real data-bearing Lazyweb MCP report depth depends on the Lazyweb account plan.

## Verify Hosted Claude Connectors

1. Enable the Lazyweb custom connector in the conversation.
2. Confirm `lazyweb_get_workflows` appears as an available tool.
3. Ask Claude to run `lazyweb_get_workflows` with `{"operation":"list","task_context":"first run Lazyweb capabilities"}`, then summarize the returned workflows as Lazyweb's super powers.

Human Lazyweb browsing and MCP setup are free. Non-Pro accounts receive partial reports and Pro accounts receive full reports; a bearer token is not proof of paid access and cannot grant purchases, spend, private user data, or destructive actions.

Use `lazyweb_search` for public pages, `lazyweb_page_tldr` for a page extract, and `lazyweb_ask_anything` for cited answers.

## Public website tools
Ask a question as an HTML page: https://www.lazyweb.com/agent/faq?q=YOUR_URL_ENCODED_QUESTION
Company agent, tools and answers: https://www.lazyweb.com/agent-access
Public MCP: https://www.lazyweb.com/mcp/public
HTTP API specification: https://www.lazyweb.com/api/public/v1/openapi.json