How do I connect in Claude?
Open PageLantern → Integrations → API & automation and choose Set up Claude. Copy the server URL from that environment. The production URL is https://pagelantern.com/api/mcp; hosted Claude requires a public HTTPS server.
In Claude, open Customize → Connectors → Add custom connector. Name it PageLantern, enter the server URL, and open the advanced OAuth settings. Use client ID pagelantern-claude and leave the client secret blank. Choose Sign in now. Your organization may require an administrator to add the connector first.
Sign in to PageLantern, check the account and current workspace displayed, then choose Allow read access. Consent uses your current PageLantern workspace; it does not offer a separate workspace chooser. Cancel returns to Claude without granting access. If your account or workspace changes while the form is open, reload and review consent again.
Back in Claude, enable PageLantern for your conversation. Ask “Summarize website health over the last 24 hours” or “Explain the latest failed check for my homepage.” If no data is available, Claude should describe that limitation rather than assume the site was healthy.
How do I use it in Claude Code?
If you connected PageLantern in Claude, sign in to Claude Code with the same active Claude subscription account and open /mcp. Claude Code can reuse that connection. This automatic sharing does not apply to API keys, auth tokens, credential helpers or third-party model providers. A local entry with the same name takes precedence.
For direct setup, copy the commands from Set up Claude Code → Claude Code: direct setup. On production, run: claude mcp add --scope user --transport http --client-id pagelantern-claude-code pagelantern https://pagelantern.com/api/mcp. Then run: claude mcp login pagelantern. Complete PageLantern sign-in and read-only consent in the browser, return to the terminal, and open /mcp to check the connection.
The user scope makes the direct connection available across your projects. Use an up-to-date Claude Code client. The public client ID is not a password. The native consent screen shows the localhost or 127.0.0.1 callback host and port on your device; only approve requests you started.
What can Claude read and explain?
The connection requests only monitors:read. It can read monitor details, retained check history, observed success, monitoring locations and graphs. Website health summaries support the last 1 hour, 6 hours, 24 hours, 7 days or 30 days, subject to retained history. They describe recorded observations and flag retention limits; they cannot infer missing checks when the historical schedule is unknown. Unknown results and periods without observations remain unknown; percentages do not prove continuous availability.
For a failed check, Claude can explain the recorded evidence and suggest what to investigate next. A failed HTTP status or timeout alone does not establish an application root cause. The connector does not read your application logs, raw response bodies, configured credentials or browser artifacts. Historical settings that were not captured with a check must remain unknown.
This Claude connection cannot run checks, create or change monitors, read client report packs, manage billing or access another workspace. Claude decides how to present returned text and images; no interactive dashboard inside Claude is promised.
How do I recover or disconnect?
If Claude asks you to reconnect, start authentication again and review the current account and workspace. Lost workspace membership cannot be restored by granting more OAuth permissions. Ask a workspace owner to check your membership when access is denied.
In PageLantern, open Integrations → API & automation → Claude & Claude Code to disconnect a connection you personally authorized. Access stops immediately for that connection; your monitors keep running. Other members manage their own connections. Previous Claude conversations are not deleted.
If setup is unavailable, the integration may not be enabled for that PageLantern environment. Custom connector access can also depend on your Claude plan and organization controls. A successful PageLantern sign-in alone does not prove the connector is configured; check its status in Claude or /mcp.
Where is my data shared?
When you ask Claude to use PageLantern, the requested monitoring outputs are sent to Anthropic. Access is tied to the approved workspace and your current membership and role. Monitor names and the sanitized website addresses returned by tools may still identify your services. Never paste passwords, API keys or session tokens into a conversation.
You can use your ordinary PageLantern sign-in method. This connection is separate from the Codex and ChatGPT plugin, which sends requested outputs to OpenAI and has its own scopes and connections. Neither provider receives access merely because you opened the setup guide.