EveryPage MCP Server

Share PDFs as tracked links and see who read them, how far they got, and where they stopped.

Local serverstdio

What is the EveryPage MCP Server?

EveryPage is an MCP integration. Share PDFs as tracked links and see who read them, how far they got, and where they stopped.

Packages and local setup

The published npm package is everypage-mcp, version 1.0.0. Its declared MCP transport is stdio.

The package declares EVERYPAGE_API_KEY (required): EveryPage API key (ep_live_...), created at https://everypage.co/account. An OAuth access token (ep_at_...) also works, limited to its granted scopes.; EVERYPAGE_BASE_URL: API origin override, for self-hosted or development instances.; EVERYPAGE_READ_ONLY: Set to true to expose only the read-only tools (no upload, no changes, no deletion)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
EVERYPAGE_API_KEYEveryPage API key (ep_live_...), created at https://everypage.co/account. An OAuth access token (ep_at_...) also works, limited to its granted scopes.Yes
EVERYPAGE_BASE_URLAPI origin override, for self-hosted or development instances.Optional
EVERYPAGE_READ_ONLYSet to true to expose only the read-only tools (no upload, no changes, no deletion).Optional