Which clients can connect?
Use a desktop or server MCP client with Streamable HTTP transport and OAuth 2.1 authorization support, including PKCE (S256), server discovery and client registration. Supported MCP protocol versions are 2025-03-26, 2025-06-18 and 2025-11-25. Browser-only clients are not supported. Compatibility depends on the client implementation and configuration; this is not a promise that every MCP app works. Clients that accept only a static API key are not supported by this connection.
Clients can register dynamically or use an HTTPS client metadata document. Callbacks use HTTPS, or HTTP loopback for a native app. Dynamic registration requires an exact callback including its port. An HTTPS metadata document may declare a portless loopback callback so the native app can choose a port; its host, path and query remain fixed. Consent binds the exact chosen return address, including its port. PageLantern does not accept wildcard callbacks. Client-provided names and metadata identify the request and are not verified publisher identities.
Claude and Claude Code have dedicated setup instructions in the Claude connection guide. Codex and ChatGPT plugin connections have their own permissions and availability in the AI app connections guide. A generic MCP connection does not imply a directory listing, provider approval or a partnership.
How do I connect?
Open Integrations → API & automation → MCP clients → Set up an MCP client. Copy the server URL for your PageLantern environment. The production URL is https://pagelantern.com/api/mcp; a remote client needs a reachable HTTPS server.
In your app, add the remote server with Streamable HTTP transport and start its OAuth sign-in. The client handles authorization discovery and registration; you do not need to paste a PageLantern password, session token or API key into the app or a conversation.
Sign in to PageLantern. Review the client-provided name, return address, signed-in account, current workspace and requested read-only permission. Only approve a connection you started in an app you trust. Client metadata is not an endorsement. Cancel returns without granting access.
Choose Allow read access, return to the client, and verify its connection status. Try asking for recent failed checks or a website health summary. A copied URL or successful account sign-in alone does not prove that the client is connected.
What can the connection read?
The generic connection requests monitors:read. It can read monitor details, retained check history, recorded availability and latency, monitoring locations, health summaries and observation graphs. Results describe recorded checks; missing observations and retention limits are not evidence of continuous uptime.
It cannot run checks, create or change monitors, pause monitoring, read client report packs, change billing or access another workspace. Configured credentials, raw response bodies and browser artifacts are not included. Failed checks can guide an investigation but do not establish an application root cause.
Who receives my monitoring data?
Requested tool outputs are returned to the MCP client you authorize. That app may send them to its AI provider according to its own settings and policies. PageLantern does not label generic clients as OpenAI or Anthropic. Monitor names and sanitized target addresses may identify your services, so review the app and destination before approving access.
The grant remains tied to your approved workspace, membership and role. Opening the setup dialog does not share monitoring data or create a grant. A local-app callback returns to your device; a hosted callback returns to the displayed HTTPS address.
How do I disconnect or recover?
Open Integrations → API & automation → MCP clients to review and disconnect the grants you personally authorized. Other members manage their own connections. Disconnecting stops future access through that grant immediately, while your monitors keep running. Information already returned to the app or included in earlier conversations is not deleted.
If your account or workspace changes while consent is open, reload and review the fresh request. If the integration is disabled for the environment, setup is unavailable. If the client cannot complete discovery, registration or authorization, check its support for the required transport and OAuth flow before trying again.