Skip to main content
Glama

@page2ai/mcp — Web to Markdown for LLM Context

npm version CI MCP Registry license MIT

No downloads badge on purpose: npm download counts are dominated by registry mirrors and bots, and this README only shows numbers a human can trust.

One-click webpage-to-Markdown MCP server for ChatGPT, Claude, and Gemini. Preserves code blocks with language hints, tables, and reading structure. Fetch, extract, convert — one tool, one command, entirely on your machine. No API key, no account, no telemetry; the only network requests are to the URLs you pass it.

Companion to the Page2AI Chrome & Firefox extensions, which convert the live page in your own browser with their own pipeline. This server is built on @page2ai/core.

Quick start

npx -y page2ai-mcp

This starts the stdio MCP server — it waits silently for a client, so wire it into one of the clients below rather than running it bare. Requires Node.js 20+. No API key. If npx ever serves you a stale cached version, run npx -y page2ai-mcp@latest once.

Updating. npx -y page2ai-mcp asks npm for the newest version each time the server starts, but an MCP client keeps the server running until you quit it: quitting and reopening the client is the update. A version named in the config (page2ai-mcp@0.6.2) stays until you change it. npx -y page2ai-mcp --version prints the version npx runs now.

page2ai-mcp is a thin unscoped wrapper around @page2ai/mcp, released together with it; its dependency is a ^ range, which on 0.x versions admits patch releases only.

Hosted endpoint (beta) — no install at all

For clients that only accept a remote MCP server URL (Streamable HTTP):

https://page2ai.igorsaevets.com/api/mcp

Same tool, same code (see remote/), rate-limited per IP. The earlier address, https://page2ai-mcp-remote.vercel.app/api/mcp, keeps answering while clients move to the new one. Privacy trade-off: URLs sent to the hosted endpoint are fetched from that server, so they transit infrastructure operated by the author (a server in New York behind Cloudflare; the earlier address runs on Vercel). Running locally via npx keeps everything on your machine — prefer it when you can.

Claude Code

claude mcp add page2ai -- npx -y page2ai-mcp

Or install the Claude Code plugin, which adds the same server plus a skill that tells the agent when to use it and what to do with signed-in, blocked and very long pages (Claude Code 2.1.275 or later):

/plugin install page2ai --marketplace igorsaevets/page2ai-mcp

It asks for one optional, secret setting, the Agent Bridge key (see below). In claude -p runs allow the tool by name: --allowedTools "mcp__plugin_page2ai_page2ai__page_to_markdown".

The repository holds two plugins, both named page2ai:

Folder

Server

Installed from

plugins/page2ai-local

this server on your computer, through npx pinned to one release, with the optional Agent Bridge

this repository's marketplace (the command above)

plugins/page2ai

the hosted endpoint https://page2ai.igorsaevets.com/api/mcp: nothing to install, no Agent Bridge, no html input, no parts; each URL goes to the author's server (privacy)

the Claude plugin directory, once its review passes; the directory accepts a local server only from organizations Anthropic has Verified

The hosted plugin's tool is mcp__plugin_page2ai_page2ai-hosted__page_to_markdown.

Claude Desktop

One-click bundle: download page2ai-mcp-<version>.mcpb from the latest release, then in Claude Desktop open Settings → Extensions → Advanced settings → Install Extension… and pick the file.

Or add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then fully quit and restart Claude Desktop:

{
  "mcpServers": {
    "page2ai": { "command": "npx", "args": ["-y", "page2ai-mcp"] }
  }
}

Cursor

Install MCP Server

Or add to ~/.cursor/mcp.json (global) / .cursor/mcp.json (project):

{
  "mcpServers": {
    "page2ai": { "command": "npx", "args": ["-y", "page2ai-mcp"] }
  }
}

VS Code (GitHub Copilot)

code --add-mcp '{"name":"page2ai","command":"npx","args":["-y","page2ai-mcp"]}'

Or add to .vscode/mcp.json:

{
  "servers": {
    "page2ai": { "type": "stdio", "command": "npx", "args": ["-y", "page2ai-mcp"] }
  }
}

Codex CLI

codex mcp add page2ai -- npx -y page2ai-mcp

Gemini CLI

gemini mcp add page2ai npx -y page2ai-mcp

Antigravity

agy mcp add page2ai npx -y page2ai-mcp

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json (macOS/Linux) or %USERPROFILE%\.codeium\windsurf\mcp_config.json (Windows):

{
  "mcpServers": {
    "page2ai": { "command": "npx", "args": ["-y", "page2ai-mcp"] }
  }
}

Zed

Add to settings.json (zed: open settings file):

{
  "context_servers": {
    "page2ai": { "command": "npx", "args": ["-y", "page2ai-mcp"] }
  }
}

Other MCP clients

Any client that speaks MCP over stdio works — Cline, Continue, JetBrains AI Assistant, LM Studio and others. Point their MCP server settings at the same command: npx -y page2ai-mcp.

Letting an AI agent install it

If an AI agent (Cline, Claude Code, Codex, …) is doing the setup for you, point it at llms-install.md — a machine-oriented install guide with the exact command per client and a verification step.

Related MCP server: clean-markdown-mcp

Tools

Tool

Description

Read-only

Example

page_to_markdown

Fetch a web page URL, or take its HTML, and convert to clean Markdown

✅

page_to_markdown(url="https://docs.anthropic.com/en/api/messages")

Long pages (0.7.0 and later)

A page longer than max_length characters (default 30,000, about 8,000 tokens) comes back in parts. A part ends between blocks: never inside a code block or the frontmatter, and never right after a heading. The first part ends with a note naming the start_index of the next part, followed by the page's sections as start_index (length): heading, so an agent can read the one section it needs:

page_to_markdown(url="https://docs.python.org/3/library/stdtypes.html")                 → part 1 and the sections
page_to_markdown(url="https://docs.python.org/3/library/stdtypes.html", start_index=N)  → the part from N

Later parts come from the text the first part was cut from, kept in the server's memory for 10 minutes after the last part was read: the site gets no new request, Agent Bridge opens no second tab, and offsets do not move. A page that fits in one part comes back exactly as before. Python's built-in types page, about 286,000 characters in one result up to 0.6.3, now comes as a first part of under 30,000 characters plus a list of its sections. The hosted endpoint returns whole pages.

When a page cannot be read (0.7.0 and later)

A fetch error keeps its first line and adds a second one with the next step. HTTP 401 and 403 (on 2026-10-30, npm, Stack Overflow, Medium and OpenAI refused the server's requests): pass the page's HTML from a browser tool as html, or turn on Agent Bridge, since the same request will be refused again; the step names PAGE2AI_BRIDGE_KEY when the server has no key, and says so when another Page2AI server holds the bridge port. 404 and 410: check the URL. 429: wait. 5xx: try later. A timeout: a larger timeout_ms. A PDF or another type that is not a page, the 10 MB cap and a redirect loop name themselves, and a host name that does not resolve says so instead of reading like an address-guard block. A page with no readable text (built by scripts in the browser) and a fetch that landed on a sign-in page come back with a note giving the same steps.

Pages behind a sign-in or rendered by JavaScript

The server fetches without cookies and runs no page scripts. For a page that needs either:

  • Pass the HTML you already have (from Playwright, Chrome DevTools MCP or another browser tool) as html, with the page's url: the HTML is converted, the URL is never fetched, and relative links resolve against it. The frontmatter then carries provenance: "HTML supplied by the caller; the source URL was not fetched". An empty html is an error, not a fetch of url.

  • Or turn on Agent Bridge in the Page2AI extension (1.6.0 or later): popup → Agent Bridge switch → allow access to websites. While the extension is connected, url pages open in a background tab of your own browser, with its cookies and scripts, and come back as the extension's Markdown (the call's include_images and include_frontmatter are honoured there, not the popup's). The extension refuses sign-in providers' pages and anything that is not http(s); a page it refuses is fetched by the server as usual, with a second text block saying why; when the browser ends on another page (a sign-in redirect), a second text block names the page it got. Private, loopback and cloud metadata addresses are refused before the browser opens them, as by the server's own fetch, and so is a page the browser was redirected to at one. The bridge listens on ws://127.0.0.1:3025 only.

    The key (0.6.0 and later). The bridge works only with the key the extension shows: popup → Agent Bridge on → Copy key. Give it to this server as PAGE2AI_BRIDGE_KEY: in Claude Desktop (the .mcpb extension) paste it into Page2AI's setting Agent Bridge key; in a JSON config add "env": { "PAGE2AI_BRIDGE_KEY": "<key>" } to the server entry; with Claude Code, claude mcp add page2ai -e PAGE2AI_BRIDGE_KEY=<key> -- npx -y page2ai-mcp. Restart the MCP client after. Several browsers or profiles: put their keys in the one variable, separated by commas; the first to connect holds the bridge. Several MCP clients running Page2AI (Claude Desktop and Cursor, say): the one started first holds port 3025 and the others run without the bridge, so give the key to each of them. Without a key the server never sends a page to a browser, and the popup and this server's log say what to paste where. On every connection both sides prove they know the key (an HMAC exchange; the key never crosses the socket), the server first: a program that took port 3025 while no server ran gets nothing from the extension, and a program that connects to the server without the key cannot ask it for pages. Firefox needs no extra setting since 0.6.0 (0.5.3 required the install's UUID in PAGE2AI_BRIDGE_ORIGINS). New key in the popup, or reinstalling the extension, makes a new key: replace the old one with it. Whoever reads your MCP client's config or the browser profile can read the key: the bridge is no stronger than your user account.

Example prompts

1. Fetch documentation and answer questions:

"Use page_to_markdown to fetch https://docs.anthropic.com/en/docs/build-with-claude/extended-thinking and summarize the three main use cases for extended thinking."

2. Extract API reference into a code snippet:

"Fetch https://ai.google.dev/gemini-api/docs/thinking with page_to_markdown, then generate a Python code sample using the thinking budget parameter."

3. Compare two documentation pages:

"Fetch both https://docs.anthropic.com/en/docs/prompt-engineering and https://platform.openai.com/docs/guides/prompt-engineering with page_to_markdown, then summarize the differences in approach."

What a call returns

Verbatim output of page_to_markdown(url="https://docs.anthropic.com/en/api/messages"), captured 2026-10-18 with core 0.2.1, truncated:

---
title: "Messages"
source: "https://platform.claude.com/docs/en/api/messages"
captured_at: "2026-10-18T04:33:07.670Z"
language: "en"
description: "API reference for Messages endpoints"
canonical: "https://platform.claude.com/docs/en/api/messages"
og_title: "Messages - Claude API Reference"
extractor: "page2ai-core"
extractor_version: "0.2.1"
---

# Messages



A beta version of this API exists and may have additional functionality. [View the beta version](https://platform.claude.com/docs/en/api/http/beta/messages).

1. [API reference](https://platform.claude.com/docs/en/api/http)

##### [Create a Message](https://platform.claude.com/docs/en/api/http/messages/create)

 POST /v1/messages

Send a structured list of input messages with text and/or image content, and the model will generate the next message in the conversation.

YAML front matter (title, source, capture timestamp, page metadata, extractor provenance), then the page as Markdown: headings, tables and fenced code preserved; navigation, header, footer and sidebars dropped. Interface buttons are left out (core 0.2.1); up to 0.3.0 this page also printed «Copy page» (with the glyph of its icon) and the «cURL» code-sample switcher, each twice. Up to 0.2.8 this URL returned the site's own Markdown copy (extractor_source: "content-negotiation"); since 0.3.0 the server reads only the page.

Configuration

No setup required — every argument has a sensible default. page_to_markdown accepts:

Argument

Type

Default

Effect

url

string

—

Absolute http(s) URL to convert. Private ranges, loopback and cloud metadata endpoints are blocked (SSRF guard). With html, not fetched: the base for relative links

html

string (≤ 10 MB)

—

The page's HTML, converted instead of a fetch. url or html is required

include_images

boolean

true

Keep ![alt](src) image references in the output

include_frontmatter

boolean

true

Prepend the YAML front matter block

timeout_ms

integer

15000

Abort the fetch after N ms (1000–60000)

max_length

integer

30000

Characters per part (100–1000000); a longer page comes back in parts

start_index

integer

0

Character offset to read from: the next part, or a section from the first part's list

The hosted endpoint takes url only (the contract its ChatGPT plugin was reviewed with), caps timeout_ms at 20000 and returns whole pages.

Environment variables of the local server, all optional:

Variable

Default

Effect

PAGE2AI_BRIDGE_KEY

—

The Agent Bridge key(s) from the Page2AI popup, comma-separated. Without one the bridge connects no browser

PAGE2AI_BRIDGE_PORT

3025

Port of the Agent Bridge on 127.0.0.1. The extension connects to 3025 only, so change it for tests, not for a browser. If it is taken (another running instance), the server starts without the bridge

PAGE2AI_BRIDGE_ORIGINS

—

Exact origins of unpacked or self-built Chrome builds the bridge accepts besides Page2AI's Web Store ID, comma-separated (chrome-extension://<id>). Firefox needs none

Planned: a profile argument (auto | docs | marketing | research | dashboard | wordpress-marketing).

Privacy

@page2ai/mcp collects no data, sends no telemetry, and makes no external network calls beyond the URLs you explicitly provide. Note that your AI client (Claude, ChatGPT, …) still sends the extracted Markdown to its own model provider under that client's privacy policy — that part is outside this server's control. See PRIVACY.md for details.

A long page's Markdown stays in the server's memory while its parts are read, until 10 minutes after the last part was read or until the server stops; nothing is written to disk.

With Agent Bridge on, the extension sends this server the URL's Markdown as your browser renders it, signed-in content included, over a WebSocket on 127.0.0.1; nothing else leaves the machine, but the Markdown then goes to your AI client like any other result.

The optional hosted endpoint is different by nature: URLs you ask it to convert are fetched from a server operated by the author (a server in New York behind Cloudflare; the earlier address runs on Vercel), and those providers keep their standard operational logs (details: privacy policy). No accounts, no tracking. If that trade-off matters for your use case, run the server locally — it is the same code.

Protocol revisions

Since 0.2.0 this server answers both MCP protocol revisions on the same stdio connection:

Revision

How a client opens the connection

Served

2026-07-28

server/discover, carrying io.modelcontextprotocol/protocolVersion in _meta

yes

2025-11-25 and earlier

the initialize handshake

yes

serveStdio picks the era from the opening message and pins one server instance for the life of the connection, so clients on older SDKs are unaffected. Note that a message carrying no version claim is treated by the specification as a 2025-era opening; server/discover without that _meta field is therefore answered with -32601 rather than being upgraded.

Verify against a build with the raw JSON-RPC frames, without a client library:

printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"server/discover","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28"}}}' | node dist/index.js

Known advisories

None. Moving to the v2 SDK removed 90 transitive packages (117 production dependencies down to 26) and with them the @hono/node-server advisory that 0.1.x carried through the monolithic @modelcontextprotocol/sdk; that package pulled the HTTP and OAuth server stack even for a stdio-only server. npm audit is clean as of 0.2.0.

Development

git clone https://github.com/igorsaevets/page2ai-mcp
cd page2ai-mcp
npm install
npm run build
node dist/index.js  # runs stdio MCP server

Test with MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Support

Pick the channel by what you have, not by what is quickest to type:

You have

Use

A bug, a page that extracts badly, a feature idea

GitHub issues — public and searchable, so the fix helps the next person too

A security vulnerability

Private vulnerability reporting, see SECURITY.md. Do not open a public issue

A usage question

Docs first, then an issue

About the author

Written and maintained by Igor Saevets — AI expert and founder of Page2AI. Full bio: igorsaevets.github.io/page2ai-docs/about/.

These are identity and collaboration links, not the support queue. A bug reported in a DM is a bug nobody else can find later, so anything you want fixed belongs in the table above.

Build provenance

An MCP server runs with the privileges of whatever launched it, so where the tarball came from is a security question, not a formality. Releases from v0.1.2 onward are published from GitHub Actions with npm provenance: each version carries a Sigstore attestation naming the commit and workflow run that produced it, recorded in the public Rekor transparency ledger and shown as a badge on npmjs.com.

Check it before you trust it:

npm audit signatures
npm view @page2ai/mcp --json | jq '.dist.attestations'

License

MIT — see LICENSE. Copyright © 2026 Igor Saevets.

Available Tools

1 tool
page_to_markdownConvert Page to MarkdownA
Read-only

Fetch a web page URL and convert it to clean Markdown optimized for LLM context. Preserves headings, code blocks (with language hints), links, and tables; keeps the main content and drops navigation, headers, footers, and sidebars. It fetches without cookies and runs no page scripts, so a page behind a sign-in or one rendered only by JavaScript comes back as its login page or with no content. For those, pass the page HTML you already have from a browser tool as html (with its url, relative links resolve and nothing is fetched), or ask the user to turn on Agent Bridge in the Page2AI browser extension 1.6.0 or later (if its popup has no Agent Bridge switch, that install is an older store version and the extension must be updated first): while it is connected, url pages open in the user's own browser with its cookies and scripts, and a page the extension declines is fetched by the server, with a note saying why. It requests only the URL given, as a browser opens a page, so docs sites return the page itself, not a Markdown copy of it; a URL that names a Markdown or text file (a raw GitHub README.md, an llms.txt) comes back as written. A long page comes back in parts (max_length, start_index), the first part listing the page's sections; pass query to get only the sections relevant to a question (BM25 ranking, no API call). A page the server cannot read comes back with the next step to take. Discovers tab groups statically and emits each panel as a ### Tab: {label} section instead of concatenating (prevents Python+TypeScript examples merging into one broken block). Zero external API calls: pages are parsed locally (linkedom) or in the user's browser.

Inputs: url, html, query, max_length, +4 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong one. Its purpose — fetch a page and emit clean Markdown — is stated explicitly and is not diluted by any sibling tool.

    Naming Consistency5/5

    The single name `page_to_markdown` is lowercase snake_case and self-describing in a source-to-format style. With one tool there is no convention mixing to penalize.

    Tool Count4/5

    One tool is genuinely sufficient for a narrow conversion service, and the surface area is absorbed by parameters (url, html, max_length, start_index, query) rather than extra tools. It is still thin — no batch or multi-URL variant — but not mismatched to the stated scope.

    Completeness4/5

    The tool covers the main lifecycle: live fetch, pre-supplied HTML fallback for auth/JS pages, long-page pagination, and query-scoped extraction. Gaps are minor, such as no batch/multi-URL conversion or a raw-HTML retrieval mode, both of which agents can work around by calling it repeatedly.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Fetches webpages or crawls sites locally, strips noise, and converts content to clean Markdown while preserving links, enabling fast, token-efficient web scraping for AI agents and LLM pipelines.
      MIT