Connect your assistant.
Keep your context.
PageFluxer’s remote MCP server lets a compatible assistant help manage monitors and read retained changes. The assistant supplies the conversation; PageFluxer supplies the monitoring and evidence.
Connect using OAuth
https://pagefluxer.com/mcp- Add a remote MCP server in your assistant using this URL. Select OAuth authentication.
- Open the PageFluxer authorization page, sign in, and select the workspace you want to connect.
- Choose read permissions. Select management or immediate-check permissions only when you want the assistant to take those actions.
- Approve the connection and return to the assistant. Try “List my PageFluxer monitors” first.
A PageFluxer REST API token is not an MCP credential. Your assistant manages its OAuth access and refresh tokens; do not paste tokens into chat.
ChatGPT
On ChatGPT web, open Plugins, choose the plus button and Add custom MCP server. Enter the URL, choose OAuth, and use client metadata (CIMD) or dynamic registration when offered. Install the resulting plugin before using it in a conversation. Availability and workspace permissions are controlled by ChatGPT.
Current OpenAI connection instructions ↗
Claude Code
claude mcp add --transport http pagefluxer https://pagefluxer.com/mcp
# In Claude Code, open /mcp and complete authentication.Current Claude Code instructions ↗
Other clients need remote Streamable HTTP and OAuth authorization code with PKCE S256. Some clients use different menu names or require an administrator to approve a server.
Available tools
| Tool | Permission | What it does |
|---|---|---|
list_monitors | Read monitors | List and filter your workspace’s monitors. |
get_monitor | Read monitors | Read configuration, baseline status and next-check time. |
create_monitor | Manage monitors | Create a text, price, stock, page-listing or PDF text monitor from a cloud preview. |
list_changes | Read changes | Filter retained changes by time, monitor or label. |
get_change | Read changes | Read a before/after pair and any existing AI summary. |
update_monitor | Manage monitors | Change the name, labels, interval, status or existing delivery switches. |
pause_monitor | Manage monitors | Pause without deleting retained history. |
run_monitor | Immediate checks | Queue an eligible Pro/Business check within current allowances. |
summarize_changes | Read changes | Build an evidence digest grouped by monitor, reusing cached summaries. |
preview_monitor / get_preview | Manage monitors | Capture public content and validate selections before saving. |
get_check | Immediate checks | See whether a requested check is queued, running or finished. |
get_usage | Read usage | Read the shared workspace’s allowances and usage. |
The first nine are the main actions; four helper tools handle previews, check receipts and usage. The server does not expose billing, invitations, member administration, integration secrets, arbitrary email recipients or new webhook destinations.
Preview → confirm → monitor
Ask for a public URL, goal and rule. Your assistant loads a cloud preview, uses the returned element candidates or whole-page selection, and confirms the interval and delivery choices with you. PageFluxer validates the selection and saves a quiet baseline. Future matching changes use your existing notification settings.
Automatic loading tries the appropriate capture method within your plan. Browser controls and recorded public steps can be passed to the preview. Your browser’s login and cookies are not inherited. Never supply passwords or confidential form inputs as recorded steps.
Changing only a name, interval or delivery switch does not require a new capture. Changing targets or capture controls does. New visual monitors and RSS/Atom/sitemap source watches, and edits to their capture configuration, currently use the web setup flow. MCP can still read, pause/resume, reschedule and toggle email/webhook delivery for those existing monitors.
On an update, the assistant supplies the current config_version as expected_version. Repeated mutation requests reuse a request_id, preventing duplicate writes within the 24-hour retry window. Preview request IDs must be UUIDs. Never change a request’s content while keeping its ID.
Webhook toggles refer to the workspace’s configured endpoint. Email toggles use the current workspace recipient and schedule. Set up destinations, custom email schedules, Slack or Teams in Notifications.
Grant only the access you need
- Read monitors: URLs, names, selections, rules, schedules and status. Recorded input values are redacted in returned configuration.
- Read changes: retained excerpts, before/after captured text and saved AI summaries. The assistant provider receives this content.
- Read usage: plan allowances and usage counters, without payment details.
- Manage monitors: capture public previews and create, update, pause or resume monitors. Owners and admins can grant this on Business.
- Immediate checks: request a manual check and read its receipt; active Pro or Business is required.
Business members can connect with read permissions. Connections remain in the selected workspace even if you switch workspaces in another tab. Owners and admins may revoke any workspace connection; members may revoke their own. A role change or removal revokes that member’s connections.
Access tokens last up to one hour and rotate through refresh tokens. Connections expire after 30 days and require a new approval. Revoke sooner under Assistant connections. Revocation stops future authorized calls; it cannot erase copies already held by your assistant provider or undo completed actions.
Tool annotations request appropriate confirmation from compatible clients. Your client controls its approval interface; granting write access authorizes it to call those tools. Captured pages and summaries are untrusted data, even when they contain instructions. Connecting an assistant does not opt a monitor into PageFluxer’s automatic OpenAI summaries.
Plans, requests and retained evidence
| Plan | MCP requests/day | Manual checks/day | Text history |
|---|---|---|---|
| Free | 100 | Not included | Up to 7 days |
| Starter | 500 | Not included | Up to 30 days |
| Pro | 2,000 | 20 | Up to 90 days |
| Business | 5,000 | 50 | Up to 180 days |
All connections share 30 MCP requests/minute and up to 20 active connections per workspace. Initialization, tool discovery and other authenticated protocol requests count; rejected or failed tool calls also count. Daily counters reset at 00:00 UTC. MCP request limits are separate from REST request limits; monitors, previews, captures, manual checks and storage keep their existing shared limits.
Lists return up to 50 records. Long text uses character-offset pagination. A digest covers up to 31 days and 50 changes per page; follow its cursor using the returned date window for more. It groups retained evidence and cached summaries without making a new OpenAI request, using an AI setup credit, or consuming an AI summary credit. Your assistant may synthesize that evidence in its own response.
Missing results can reflect retention, a paused monitor, a failed capture or filters. They are not proof that a website did not change. A queued manual check is not proof of a successful capture. View monitor details for delivery health and advanced diagnostics.
If a connection or tool call fails
- Permission required: reconnect and approve the named scope. Check that your workspace role can grant it.
- Expired or revoked: sign in again and authorize a new connection. A replayed refresh token also revokes its connection.
- Preview loading or timed out: keep the preview request UUID and retry the same request, or ask for the saved preview state. Do not assume a capture succeeded.
- Selection missing or ambiguous: load a fresh preview and choose a returned candidate. Check the capture guide.
- Version conflict: read the monitor again and confirm the latest changes before editing.
- Allowance or cooldown: read usage and the error’s retry time. MCP cannot override plan limits or failure backoff.
- Server disabled: normal PageFluxer monitoring continues; try connecting later or contact support.
PageFluxer retains aggregate MCP operation counts for 90 days and short-lived retry receipts for 24 hours. Captured content, prompts and tokens are not sent to analytics. Read about data handling →