Skip to main content
Glama

everypage-mcp

MCP server for EveryPage. Lets an AI assistant turn a PDF into a tracked share link, and tell you who actually read it — how far they got, how long they spent, and which page they stopped on.

"Share this proposal with Jane and Bob, then tell me tomorrow whether either of them read past the pricing page."

§ 01 Install

No install: the hosted server. EveryPage also runs this server at https://everypage.co/mcp (Streamable HTTP, OAuth sign-in, no API key). In Claude, open Customize → Connectors → Add custom connector and paste that URL; in Claude Code, claude mcp add --transport http everypage https://everypage.co/mcp. See everypage.co/integrations/claude. Uploads there take an https link rather than a local file path.

This package (stdio). Get an API key from everypage.co/account — it looks like ep_live_…. Then point your client at the server.

Claude Code

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

Claude Desktop, Cursor, VS Code, and anything else that reads a JSON config

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

Requires Node 20 or newer.

Related MCP server: Docalyze

§ 02 What it can do

Tool

What it does

everypage_share_pdf

Upload a PDF (local path or https URL) and get a tracked link, embed code and QR URL — applying share settings in the same call

everypage_list_files

List documents, optionally filtered by name

everypage_get_file

One document's links, protection and status

everypage_update_file_settings

Change passcode, expiry, downloads, viewer mode, email gate, view limit, page range, slug

everypage_delete_file

Trash a document, or purge it permanently

everypage_replace_content

Swap the PDF behind a live link, keeping the link and its history · Pro

everypage_get_readership

Who read it, how far they got, where they dropped off

everypage_list_events

Recent reads, downloads or captured leads, with a polling cursor

everypage_create_variants

One tracked link per recipient, so reads are attributed by name · Pro

everypage_list_variants

Those links and their status

everypage_update_variant

Rename, revoke or restore one recipient's link · Pro

everypage_delete_variant

Delete it, or GDPR-redact the recipient's name · Pro

everypage_list_webhooks

Webhook endpoints and their delivery health

everypage_manage_webhook

Create, test or delete a webhook endpoint

everypage_account

The connected account, its plan, and what that plan allows

Two prompts ship as slash commands: readership_digest (what happened over the last N days) and send_tracked_copies (one link per recipient, done right).

§ 03 Things worth knowing

Any way of naming a document works. Every tool that takes a file accepts a UUID, a short link id, or a share URL pasted straight out of the browser — including /embed/ links and ones carrying ?via= — so there is no need to look up an id first.

Uploads stream. A local path is read off disk rather than into memory, so a 2 GB document on the Pro plan uploads without the process growing. Files are checked for the PDF magic bytes and against your plan's size cap before anything is sent.

A URL is fetched without your credentials. The url lane downloads from the host you named using no EveryPage headers at all, then uploads the bytes. Your API key never travels to a third-party host.

Readership is summarized, not dumped. The tool computes the finding — the steepest drop in the reach funnel, the most re-read page — and puts the raw rows in structuredContent for anything that wants to chart them.

Event cursors are per-stream. everypage_list_events returns a nextCursor, and it is only valid for the same type. The three streams have independent id sequences; crossing them silently returns the wrong window.

Deleting is reversible by default. everypage_delete_file trashes, and says so; purge: true is the irreversible one. Tools that cannot be undone are marked with MCP's destructiveHint, so clients that support confirmation prompts will ask before running them.

§ 04 Configuration

Variable

Required

Default

Meaning

EVERYPAGE_API_KEY

yes

—

ep_live_… API key, or an ep_at_… OAuth token (limited to its granted scopes)

EVERYPAGE_BASE_URL

no

https://everypage.co

API origin, for self-hosted or development instances

EVERYPAGE_READ_ONLY

no

false

true exposes only the seven read-only tools

§ 05 Plans

Some features are plan-gated, and a refusal will say which plan is needed. everypage_account reports the current plan and what it locks.

Free

Basic

Pro

Upload size

20 MiB

200 MiB

2 GiB

Live documents

3

100

unlimited

Tracked links, share settings, webhooks

✓

✓

✓

Passcode, view limits, view notifications, per-page stats

✓

✓

Per-recipient links, email-capture gate, content replacement, watermarks, page ranges

✓

The API allows 120 requests per minute per key.

§ 06 Not included

/files/claim and the Canva publishing lane (app plumbing, not agent work), branding assets and hotspots (large Pro payloads with no natural agent use), and the authenticated QR fetch — the qr_url every tool returns is public and needs no credentials. Open an issue if you want any of them.

§ 07 Development

npm ci
npm run typecheck
npm test
npm run build
npm run inspector      # drive the tools by hand in the MCP inspector

The tool surface is snapshotted in test/schemas.test.ts: renaming a tool or one of its inputs fails CI on purpose, because it breaks every saved prompt and agent config that names it.

Field names and output shapes are pinned by the cross-integration contract shared with the EveryPage Zapier, Make and n8n integrations — change that first.

License

MIT

Available Tools

15 tools
everypage_accountAccount and planA
Read-only
Inspect

The connected EveryPage account: which email it belongs to, which plan it is on, and what that plan allows (upload size, document count, and which features are locked). Check this before attempting a plan-gated action.

Inputs: no named parameters. Returns: name, plan, email, lockedFeatures, +3 more

everypage_create_variantsCreate per-recipient linksAInspect

Mint one tracked link per recipient for a document, so each person's reads are attributed to them by name instead of blending into one anonymous total. Pass every recipient in a single call. Each link can also override the document's download permission or page range for that person. Requires the Pro plan.

Inputs: file (required), recipients (required). Returns: failed, created, fileUuid, variants, +1 more

everypage_delete_fileDelete a documentA
DestructiveIdempotent
Inspect

Move an EveryPage document to the trash so its share link stops working. Trashed documents can be restored from the EveryPage dashboard. Set purge to true to destroy it permanently instead - that cannot be undone.

Inputs: file (required), purge. Returns: uuid, purged, trashed

everypage_delete_variantDelete or redact a per-recipient linkA
DestructiveIdempotent
Inspect

Permanently delete a per-recipient link, or - with redact - erase the recipient's name everywhere while leaving the link working and the readership intact. Redaction is the right answer to a GDPR erasure request; a redacted name can never be set again. Both are irreversible. Requires the Pro plan.

Inputs: file (required), variant (required), redact. Returns: deleted, fileUuid, redacted, variantUuid

everypage_get_fileGet a documentA
Read-only
Inspect

Look up one EveryPage document and report its share links, how it is protected, and whether it is still live. Accepts a UUID, a short link id, or a share URL pasted straight from the browser.

Inputs: file (required). Returns: file, uuid, qr_url, shortId, +3 more

everypage_get_readershipGet a document's readershipA
Read-only
Inspect

Find out who read an EveryPage document and how far they got: views, unique readers, read time, completion rate, countries, where readers dropped off, and per-recipient attribution. Use this to answer questions like "did they read my proposal?" or "where do people stop reading?".

Inputs: file (required), includePages, includeProofing. Returns: tier, pages, funnel, fileName, +23 more

everypage_list_eventsList recent read activityA
Read-only
Inspect

Recent activity across the account's EveryPage documents: view sessions, downloads, or leads captured by the email gate. Returns a cursor so a later call can fetch only what has happened since. Use this to answer "has anyone read anything today?" or to poll for new reads.

Inputs: file, type, limit, since. Returns: type, count, events, nextCursor

everypage_list_filesList documentsA
Read-only
Inspect

List the EveryPage documents on this account, newest first, with their share links and view counts. Use query to filter by name when looking for a particular document.

Inputs: limit, query. Returns: files, shown, totalCount

everypage_list_variantsList per-recipient linksA
Read-only
Inspect

List a document's per-recipient links with their recipient labels, URLs, and whether they have been revoked or GDPR-redacted. Requires the Pro plan.

Inputs: file (required). Returns: count, fileUuid, variants

everypage_list_webhooksList webhook endpointsA
Read-only
Inspect

List the account's webhook endpoints, what events each receives, and whether deliveries are healthy. Signing secrets are never retrievable - they are shown once, when the endpoint is created. Use this to diagnose an automation that has stopped firing.

Inputs: no named parameters. Returns: count, webhooks

everypage_manage_webhookCreate, test or delete a webhookA
Destructive
Inspect

Manage where EveryPage sends event notifications. Create an endpoint to receive signed deliveries when a document is opened, read, downloaded or a lead is captured; send a test delivery to check an endpoint is reachable; or delete one. Creating returns a signing secret that is shown only once.

Inputs: action (required), url, file, events, +2 more. Returns: action, secret, status, deleted, +3 more

everypage_replace_contentReplace a document's contentA
Destructive
Inspect

Swap the PDF behind an existing EveryPage link, keeping the same share link, QR code, settings and readership history - only the bytes change. Anyone who already has the link sees the new version. This is also the way to revive a link that was burned by its view limit. The previous version is not recoverable. Requires the Pro plan.

Inputs: file (required), url, path, keepAnchors. Returns: uuid, qr_url, shortId, fileName, +3 more

everypage_share_pdfShare a PDFAInspect

Upload a PDF to EveryPage and get back a tracked share link, an embeddable iframe, and a QR code URL. Give either path (a PDF on this machine) or url (an https link to a PDF). Share settings such as a passcode, expiry or download permission can be applied in the same call. Every read of the resulting link is tracked - use everypage_get_readership afterwards to see who read it.

Inputs: url, path, slug, pageTo, +13 more. Returns: size, uuid, qr_url, shortId, +6 more

everypage_update_file_settingsChange a document's share settingsA
Idempotent
Inspect

Change how an existing EveryPage document is shared: passcode, expiry, downloads, viewer mode, email gate, view limit, page range or vanity slug. Settings that are not mentioned keep their current value.

Inputs: file (required), slug, pageTo, pageFrom, +12 more. Returns: file, uuid, qr_url, shortId, +4 more

everypage_update_variantUpdate a per-recipient linkA
Idempotent
Inspect

Rename, revoke or restore a per-recipient link, or change what that one recipient may do. Revoking makes their link stop working while leaving everyone else's alone; it can be undone. Requires the Pro plan.

Inputs: file (required), variant (required), label, pageTo, +3 more. Returns: url, variant, fileUuid

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (files, variants, webhooks, account). A few pairs overlap in surface intent — get_readership vs list_events (both about reading activity) and delete_variant vs update_variant (both can revoke a link) — but the descriptions draw the boundaries clearly enough to disambiguate.

    Naming Consistency5/5

    All tools use a consistent everypage_ prefix with a snake_case verb_noun pattern (list_files, get_file, update_file_settings, create_variants, list_webhooks). Minor wording differences like share_pdf and manage_webhook don't break the predictable convention.

    Tool Count5/5

    15 tools is well within the well-scoped range and each earns its place: file CRUD, variant lifecycle, webhooks, analytics, and account. No obvious redundancy or filler.

    Completeness4/5

    Covers the full document lifecycle (upload/share, list, get, settings, replace, delete/trash) plus variants, webhooks, readership, events, and account info. Minor gaps exist (e.g. no explicit restore-from-trash tool despite delete mentioning it, no per-variant get), but core workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers