@page2ai/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| page_to_markdownA | 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection; the tool's purpose (fetch a URL or supplied HTML and return clean Markdown) is unambiguous and self-contained. No sibling tools overlap with it.
A single snake_case verb_noun name (page_to_markdown) that precisely describes the action and target. There is no mixed convention to detract from it.
The tool is genuinely multi-purpose (URL fetch, raw HTML passthrough, browser bridge fallback, paginated output) so one tool is defensible, but a single-tool surface is thin and users may expect at least a batch or metadata companion. Borderline rather than clearly well-scoped.
For a page-to-Markdown domain it covers the main paths: direct fetch, HTML you already have, browser-authenticated fetch, long-page pagination, and error guidance. Minor gaps exist (e.g. no explicit batch/multi-URL conversion), but agents can work around them by calling repeatedly.