Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Share PDFs as tracked links and see who read them, how far they got, and where they stopped.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
EVERYPAGE_API_KEY, EVERYPAGE_BASE_URL, EVERYPAGE_READ_ONLYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://everypage.co/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"everypage": {
"command": "npx",
"args": [
"-y",
"everypage-mcp"
],
"env": {
"EVERYPAGE_API_KEY": "your-value",
"EVERYPAGE_BASE_URL": "your-value",
"EVERYPAGE_READ_ONLY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http everypage https://everypage.co/mcpclaude mcp add everypage --env EVERYPAGE_API_KEY=your-value --env EVERYPAGE_BASE_URL=your-value --env EVERYPAGE_READ_ONLY=your-value -- npx -y everypage-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"everypage": {
"url": "https://everypage.co/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"everypage": {
"command": "npx",
"args": [
"-y",
"everypage-mcp"
],
"env": {
"EVERYPAGE_API_KEY": "your-value",
"EVERYPAGE_BASE_URL": "your-value",
"EVERYPAGE_READ_ONLY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"everypage": {
"type": "http",
"url": "https://everypage.co/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"everypage": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"everypage-mcp"
],
"env": {
"EVERYPAGE_API_KEY": "your-value",
"EVERYPAGE_BASE_URL": "your-value",
"EVERYPAGE_READ_ONLY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://everypage.co/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
EVERYPAGE_BASE_URL envEVERYPAGE_READ_ONLY envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain everypage.co (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: EVERYPAGE_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.1.1) reached the registry 22 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Toggl 2.0
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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."
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.
| 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).
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.
| 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 |
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.
/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.
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.
MIT