
EveryPage
co.everypagePublished by everypage.coOfficial publisherv1.1.1Updated Oct 30, 2026
Share PDFs as tracked links and see who read them, how far they got, and where they stopped.
Overview
EveryPage MCP server that lets an assistant share PDFs as tracked links and report who read them, how far they got, and where they stopped.
- What you can do
- Upload and share PDFs: upload a local file or https URL and get a tracked link, embed code and QR URL with share settings applied
- Manage documents: list and inspect documents, change passcode, expiry, downloads, viewer mode, email gate, view limit, page range or slug, replace the PDF behind a live link, and trash or purge
- Readership reporting: see who read a document, how far they got and where they dropped off, and poll recent reads, downloads or captured leads with a cursor
- Per-recipient links: create one tracked link per recipient, list them, rename, revoke, restore or delete them, or redact a recipient's name
- Webhooks and account: list, create, test or delete webhook endpoints and…
- When to use it
- Useful when you send proposals, reports or other PDFs to specific people and want the assistant to create tracked share links and later report who actually read them and how far. Also fits workflows that need per-recipient attribution or lead capture on documents.
- Requirements
- Either the hosted remote endpoint with OAuth sign-in, or the local npm package everypage-mcp over stdio, which needs Node 20 or newer. The local package requires an EveryPage API key in EVERYPAGE_API_KEY (an OAuth access token also works). Optional EVERYPAGE_BASE_URL for self-hosted instances and EVERYPAGE_READ_ONLY to expose only read-only tools. An EveryPage account and plan apply; upload size and features are plan-gated.
Installation
In SourceWeft
- Open EveryPage in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/co.everypage%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"everypage": {
"type": "http",
"url": "https://everypage.co/mcp"
}
}
}README
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 Desktop, Cursor, VS Code, and anything else that reads a JSON config
Requires Node 20 or newer.
§ 02 What it can do
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
§ 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.
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
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.
§ 08 Links
License
Source: README.md at commit d4b5712
Tools
0Version history
3- v1.1.1LatestOct 15, 2026
- v1.1.0Oct 9, 2026
- v1.0.0Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts