Free plan

MCP server for AI assistants

Connect Claude, ChatGPT, Cursor or any MCP client to EveryPage, hosted at everypage.co/mcp or run locally, so it can share PDFs as tracked links and report who read them.

The EveryPage MCP server lets an AI assistant use your EveryPage account: upload a PDF and hand back a tracked share link, then answer questions about who read it and how far they got.

It speaks the Model Context Protocol, so it works with any MCP client — Claude on the web, desktop and mobile, Claude Code, ChatGPT, Cursor, VS Code, and others. There are two ways to run it:

  • Hosted, at https://everypage.co/mcp. Nothing to install: the client signs in with your EveryPage account over OAuth. This is the only way to use it from claude.ai, the Claude mobile apps and ChatGPT.
  • Local, from npm as everypage-mcp, launched by your client with an API key. It is open source (MIT), and it can read a PDF straight off your disk.

Both offer the same tools, except everypage_publish_html, which only the hosted server has. The MCP registry entry is co.everypage/mcp, and the same manifest is served at /.well-known/mcp.json for agents that discover servers by well-known URL.

Hosted server

The endpoint is https://everypage.co/mcp, served over the streamable HTTP transport (stateless, JSON responses; POST only).

Claude (claude.ai, Claude Desktop, and the iOS and Android apps once added): open Customize → Connectors, choose Add custom connector, name it EveryPage, paste the URL, then Add and Connect. Approve the EveryPage consent screen that opens. Free Claude plans allow one custom connector. Step by step: Claude connector.

ChatGPT (on the web, on a plan that allows custom MCP servers): open Plugins at chatgpt.com/plugins, click +, choose Add custom MCP server, name it EveryPage, paste the URL and choose OAuth, then Create as a plugin and approve the EveryPage consent screen. In a chat, type @ and pick EveryPage. If the option to add a server is missing, turn on developer mode in ChatGPT's settings; in a Business or Enterprise workspace an admin may have to allow it. Step by step: ChatGPT connector.

Claude Code

claude mcp add --transport http everypage https://everypage.co/mcp

Then run /mcp inside Claude Code and choose to authenticate. Claude Code receives its authorization code on a local port; EveryPage's consent screen says so ("an app on this computer is asking for access").

Any other client that supports remote MCP servers takes the same URL.

How sign-in works

The hosted server is an OAuth 2.1 protected resource. Nothing needs registering by hand:

  1. An unauthenticated request gets 401 with WWW-Authenticate: Bearer resource_metadata="https://everypage.co/.well-known/oauth-protected-resource/mcp".
  2. That protected resource metadata (RFC 9728) names https://everypage.co/mcp as the resource and https://everypage.co as its authorization server, whose RFC 8414 metadata lists a registration_endpoint.
  3. The client registers itself at POST /oauth/register (RFC 7591 dynamic client registration), then runs the authorization-code flow with PKCE, passing resource=https://everypage.co/mcp (RFC 8707).
  4. You sign in to EveryPage and approve the request. The token the client gets is bound to /mcp; it is refreshed in the background and rotates on every refresh.

The details are in OAuth apps and oEmbed.

Scopes

The consent screen lists what the client asks for, and you approve it as a whole. A client that asks for nothing specific gets the scopes it registered for, all five by default:

ScopeLets the client
files:readList your documents, their share links and settings
files:writeShare a PDF from a link, change settings, replace content, trash or delete documents
readership:readRead readership summaries and the events feed
profileRead your account email and plan
webhooks:manageList, create, test and delete webhooks

Tools that need a scope the grant lacks are not offered at all, so a read-only grant shows only read-only tools.

Using an API key instead

A client that cannot run a browser sign-in can send an API key as a header. Keys hold every scope.

claude mcp add --transport http everypage https://everypage.co/mcp --header "Authorization: Bearer ep_live_..."

Disconnecting

Click Disconnect on the Claude or ChatGPT card in account settings, or Revoke the app under Connected apps. The client's tokens stop working at once. Remove the connector in the client too (in Claude, Customize → Connectors; in ChatGPT, under Plugins), or it keeps offering a connection that now fails.

What differs from the local package

The hosted tools take an https link to a PDF wherever the local package takes a file path: everypage_share_pdf and everypage_replace_content fetch the link on EveryPage's side. A file attached to a chat is not reachable by a connector; upload it at everypage.co first, and everypage_list_files finds it by name.

The hosted server also has everypage_publish_html, which takes a page's HTML inline, so Claude can publish an artifact (or ChatGPT a canvas page) it wrote in the conversation. The page must be one self-contained HTML document of at most 3 MB; a React component has to be rewritten as HTML first. It goes through the same lane as an HTML upload: your plan's size cap, the upload scan (a page the scan holds is published but paused for review, and the tool says so) and the HTML settings: expiry, passcode and view limit (Basic), email gate and allowed domains (Pro). Readership for a page is views, readers and time.

EveryPage records which tools are called and how many fail, per account, to run the service. It never records tool arguments or results.

Local server

Create an API key in your account settings — it starts with ep_live_ and is shown once — then point your client at the package.

Claude Code

claude mcp add everypage --env EVERYPAGE_API_KEY=ep_live_... -- npx -y everypage-mcp

Everything that reads a JSON config (Claude Desktop, Cursor, VS Code, …)

{
  "mcpServers": {
    "everypage": {
      "command": "npx",
      "args": ["-y", "everypage-mcp"],
      "env": { "EVERYPAGE_API_KEY": "ep_live_..." }
    }
  }
}

The server runs locally, launched by your client — there is nothing to host. It needs Node 20 or newer. Because it runs on your machine, it can read a PDF straight off your disk when you ask it to share one.

Configuration

VariableRequiredDefaultMeaning
EVERYPAGE_API_KEYyes—An API key (ep_live_…), or an OAuth access token (ep_at_…) limited to its granted scopes
EVERYPAGE_BASE_URLnohttps://everypage.coAPI origin override, for development instances
EVERYPAGE_READ_ONLYnofalsetrue exposes only the read-only tools — nothing can upload, change or delete

Tools

Fifteen tools on both servers, plus everypage_publish_html on the hosted one, grouped by what you would actually ask for.

Documents — everypage_share_pdf (upload from a path or URL — a URL only on the hosted server — and return the share link, embed code and QR URL, applying share settings in the same call), everypage_list_files, everypage_get_file, everypage_update_file_settings, everypage_delete_file, everypage_replace_content (Pro), and on the hosted server everypage_publish_html (publish an HTML page passed inline and return the same link, embed code and QR URL).

Readership — everypage_get_readership (a summary: readers, read time, completion, countries, drop-off page, most re-read page) and everypage_list_events (recent reads, downloads or captured leads, with a polling cursor).

Per-recipient links (Pro) — everypage_create_variants, everypage_list_variants, everypage_update_variant, everypage_delete_variant.

Account and delivery — everypage_list_webhooks, everypage_manage_webhook, everypage_account.

Two prompts ship as slash commands: readership_digest and send_tracked_copies.

Behaviour worth knowing

Any way of naming a document works. Every tool taking a document accepts a UUID, a short link id, or a share URL pasted from the browser — including /embed/ links and ones with ?via= on the end.

Your key stays local. With the local package, it lives in your MCP client's config and is sent only to everypage.co. When you ask the server to share a PDF from a third-party URL, that download is made with no EveryPage credentials attached.

Uploads stream and are checked first. A local file is read off disk rather than into memory; a linked one is streamed to disk on the server. Either way it is verified as a PDF and checked against your plan's size cap before it is stored.

Deleting is reversible by default. everypage_delete_file trashes the document; permanent destruction needs an explicit purge. Irreversible tools are marked with the protocol's destructiveHint, so clients that support confirmation prompts ask first. Set EVERYPAGE_READ_ONLY=true (local) or grant only read scopes (hosted) if you want write tools withheld entirely.

Event cursors are per stream. everypage_list_events returns a nextCursor valid only for the same type — the view, download and gate streams have independent id sequences. See Events feed.

Plan gating

The server works on every plan; what it can do follows the account. Sharing documents and reading readership work on free. Passcodes, view limits, read notifications and page-level statistics need Basic. Per-recipient links, the email-capture gate, content replacement, watermarks and page ranges need Pro. A refusal always names the plan required, so the assistant can tell you rather than retrying.