everypage-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERYPAGE_API_KEY | Yes | ep_live_… API key, or an ep_at_… OAuth token (limited to its granted scopes) | |
| EVERYPAGE_BASE_URL | No | API origin, for self-hosted or development instances | https://everypage.co |
| EVERYPAGE_READ_ONLY | No | true exposes only the seven read-only tools | false |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| everypage_share_pdfA | Upload a PDF to EveryPage and get back a tracked share link, an embeddable iframe, and a QR code URL. Give either |
| everypage_list_filesA | List the EveryPage documents on this account, newest first, with their share links and view counts. Use |
| everypage_get_fileA | 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. |
| everypage_update_file_settingsA | 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. |
| everypage_delete_fileA | 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. |
| everypage_replace_contentA | 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. |
| everypage_get_readershipA | 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?". |
| everypage_list_eventsA | 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. |
| everypage_create_variantsA | 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. |
| everypage_list_variantsA | 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. |
| everypage_update_variantA | 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. |
| everypage_delete_variantA | 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. |
| everypage_list_webhooksA | 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. |
| everypage_manage_webhookA | Manage where EveryPage sends event notifications. Create an endpoint to receive signed deliveries when a document is 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. |
| everypage_accountA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| readership_digest | Summarize who read which documents recently, and what changed. |
| send_tracked_copies | Mint a separate tracked link for each recipient of a document, so reads are attributed by name. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/EveryPageApp/everypage-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server