URLpipe MCP server
Commit Oct 12, 2026Lets an AI agent render JavaScript-heavy web pages to extract Markdown, screenshots, PDFs, metadata, and Lighthouse audits.
Also known as URLpipe/mcp, mcp
- Stars
- 0
- Tools
- 17
- Downloads, 30 days
- —
- Latest version
- 1.4.0
- Last commit
- Oct 12, 2026
- License
- MIT
What is URLpipe MCP?
URLpipe lets an AI agent render JavaScript-heavy web pages to extract Markdown, screenshots, PDFs, metadata, and Lighthouse audits. It exposes 17 tools, such as list_projects, get_usage, fetch_markdown.
Summary generated from the project's README
About URLpipe MCP server
URLpipe provides a hosted MCP server that allows AI agents to interact with modern, JavaScript-heavy websites. Unlike standard fetch tools that only retrieve an empty HTML shell from React or Vue applications, this server uses a real Chrome instance to render pages fully before processing them. This enables agents to see exactly what a human user sees in a browser.
The service is accessed via a streamable HTTP connection at urlpipe.dev/mcp, making it compatible with clients like Claude Desktop, Cursor, VS Code, and Windsurf. Users connect by providing a bearer token obtained from the URLpipe dashboard. The server includes 17 different tools for various tasks, including fetching content as Markdown, capturing screenshots, generating PDFs, and running Lighthouse audits for performance and SEO.
Data processing and storage occur within the EU. The system operates on a credit-based model where users receive 1,000 free credits every month. To manage costs, the server supports cached results which do not consume credits, and users can choose between asynchronous requests or using the sync parameter to wait for a result.
What you can do with it
- 1Extract content from dynamic sitesAn agent can read the main content of a React or Vue dashboard by converting the rendered page into clean Markdown.
- 2Perform web performance auditsA developer can request a full health report including Lighthouse scores and Core Web Vitals for a specific URL.
- 3Capture visual representations of pagesAn AI can take a full-page screenshot or generate a PDF to visually inspect a website's layout.
- 4Scrape structured data from web pagesYou can instruct an agent to pull specific product details or prices into a custom schema.
Written from the project's README. Every use case is checked against a quote from it.
How to install URLpipe MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall URLpipe MCP in Claude Code
$ claude mcp add --transport http mcp https://urlpipe.dev/mcpInstall URLpipe MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://urlpipe.dev/mcp"
}
}
}Install URLpipe MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://urlpipe.dev/mcp"
}
}
}Install URLpipe MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://urlpipe.dev/mcp"}'Install URLpipe MCP in Codex
$ codex mcp add mcp --url https://urlpipe.dev/mcpInstall URLpipe MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] url = "https://urlpipe.dev/mcp"
Install URLpipe MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp https://urlpipe.dev/mcpInstall URLpipe MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://urlpipe.dev/mcp",
"type": "http"
}
}
}URLpipe MCP tools 17
Detected from the READMElist_projectsget_usagefetch_markdownfetch_htmlcapture_screenshotcapture_pdfcapture_console_errorsrun_lighthouse_auditextract_metadatadetect_technologiesextract_keywordssummarize_page
| list_projects | — | |
| get_usage | — | |
| fetch_markdown | — | |
| fetch_html | — | |
| capture_screenshot | — | |
| capture_pdf | — | |
| capture_console_errors | — | |
| run_lighthouse_audit | — | |
| extract_metadata | — | |
| detect_technologies | — | |
| extract_keywords | — | |
| summarize_page | — |
Show all 17 toolsShow fewer tools
extract_datascrape_urlget_resultlist_requestsget_request
| extract_data | — | |
| scrape_url | — | |
| get_result | — | |
| list_requests | — | |
| get_request | — |
Configuration
URLPIPE_AUTH
| Name | Description | |
|---|---|---|
| URLPIPE_AUTH | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableurlpipe/mcp is public and reachablegithub.com/urlpipe/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-12github.com/urlpipe/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 121 msPass
README
View on GitHubA plain fetch tool does an HTTP GET. On a site that builds itself in the browser —
React, Vue, most docs sites and dashboards — that returns an empty shell, and the agent
either says it can't read the page or guesses what was on it.
URLpipe loads every page in real Chrome first, then hands your agent what it asked for: the page as Markdown, a screenshot it can look at, a PDF, its metadata, data in a schema you define, its console errors or a Lighthouse audit.
- Hosted. Streamable HTTP at
https://urlpipe.dev/mcp. Nothing to install or run. - One bearer token. Can be read-only, limited to one project, or set to expire.
- 17 tools. Every API operation, plus results, request history, projects and usage.
- Same credits as the HTTP API. 1,000 free every month, no card. Cached results cost nothing.
- Processed in the EU. Fetching, rendering and storage happen in Europe.
This repository holds the server's registry entry (server.json) and
the setup for each client. The server itself runs at urlpipe.dev.
Get a token
- Sign up and confirm your email address.
- In the dashboard, open Organization → MCP access and create a token. Choose Fetch pages and read results for an agent that works normally, or Read past results only for one that must never spend credits.
- Copy it — it is shown once.
Every client sends it as Authorization: Bearer YOUR_TOKEN.
Connect your client
Claude Code
claude mcp add --transport http urlpipe https://urlpipe.dev/mcp \
--scope user \
--header "Authorization: Bearer YOUR_TOKEN"
Or share it with your team in .mcp.json, each person setting their own URLPIPE_TOKEN:
{
"mcpServers": {
"urlpipe": {
"type": "http",
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer ${URLPIPE_TOKEN}"
}
}
}
}
Claude Desktop
Where your organization has request headers in Customize → Connectors → Add custom
connector, add https://urlpipe.dev/mcp with No sign-in and an authorization
header of Bearer YOUR_TOKEN. Otherwise use the open-source
mcp-remote bridge in
claude_desktop_config.json (needs Node.js):
{
"mcpServers": {
"urlpipe": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://urlpipe.dev/mcp",
"--header",
"Authorization:${URLPIPE_AUTH}",
"--transport",
"http-only"
],
"env": {
"URLPIPE_AUTH": "Bearer YOUR_TOKEN"
}
}
}
}
Cursor
~/.cursor/mcp.json, or .cursor/mcp.json in a project:
{
"mcpServers": {
"urlpipe": {
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer ${env:URLPIPE_TOKEN}"
}
}
}
}
VS Code
.vscode/mcp.json — VS Code asks for the token once and stores it securely:
{
"inputs": [
{
"type": "promptString",
"id": "urlpipe-token",
"description": "URLpipe MCP token",
"password": true
}
],
"servers": {
"urlpipe": {
"type": "http",
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer ${input:urlpipe-token}"
}
}
}
}
Windsurf
mcp_config.json:
{
"mcpServers": {
"urlpipe": {
"serverUrl": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer ${env:URLPIPE_TOKEN}"
}
}
}
}
Cline
cline_mcp_settings.json:
{
"mcpServers": {
"urlpipe": {
"type": "streamableHttp",
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
},
"disabled": false,
"autoApprove": ["list_projects", "get_usage", "get_result"]
}
}
}
Zed
settings.json:
{
"context_servers": {
"urlpipe": {
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
From a directory
URLpipe is listed on Smithery,
Glama and
cursor.directory (as a Cursor plugin), and in
the official MCP Registry as dev.urlpipe/mcp. On Smithery, paste your token as it is — the server
accepts it with or without the Bearer prefix.
Step-by-step pages for each client, with a first prompt to try and troubleshooting, are at urlpipe.dev/integrations.
Tools
| Tool | What it returns | Credits |
|---|---|---|
list_projects |
The projects the token can reach. Start here: every fetching tool takes a project_id. |
0 |
get_usage |
What the plan allows, what is left this period, and what each operation costs. | 0 |
fetch_markdown |
The page's main content as clean Markdown, after its JavaScript ran. The one to use for reading. | 1 |
fetch_html |
The rendered DOM — what a browser sees, not the shell curl gets. | 1 |
capture_screenshot |
A full-page screenshot, returned as an image the model can look at. Viewport, device scale, dark mode, one element by selector, PNG/JPEG/WebP. | 1 |
capture_pdf |
The whole rendered page as a PDF, with its web fonts and lazy-loaded images in. Paper size, orientation, margins, scale, the print or on-screen stylesheet. | 1 |
capture_console_errors |
console.error and console.warn during load, uncaught exceptions and unhandled promise rejections. |
1 |
run_lighthouse_audit |
A real Lighthouse audit: performance, accessibility, best practices, SEO and Core Web Vitals. | 2 |
extract_metadata |
Everything the page declares about itself — Open Graph, Twitter cards, JSON-LD, meta tags — in one object with the same keys for every page: title, authors, dates, share image, icons, feeds and more. | 1 |
detect_technologies |
What the site is built with — CMS, frameworks, analytics, CDN, web server — each with its version, a confidence and the signals that gave it away. | 1 |
extract_keywords |
The 5–15 terms that best represent the page, ranked by a language model. | 15 |
summarize_page |
A short Markdown summary of the page's main content. | 17 |
extract_data |
Data from the page in a schema you define: name the fields and get back exactly those keys, null where the page gives no value. Product details, prices, contact data, lists of items. | 24 |
scrape_url |
Several of the above from one page visit. Each operation is billed as usual. | sum |
get_result |
The result of an earlier request, by its token. | 0 |
list_requests |
A project's recent requests, newest first. | 0 |
get_request |
Everything about one past request except its result: timings, cache, webhook delivery. | 0 |
Async is the default, as it is over HTTP: a fetching tool returns a token straight
away and get_result collects the result. Pass sync: true to wait for it instead.
Most agents work this out from the tool descriptions; saying "use sync: true" in the
prompt saves a round trip.
A repeated request is free. Results are kept for 30 days and reused while they are
fresher than max_age (7 days by default).
Prompts and resources
Clients that show MCP prompts (often as slash commands) get three ready-made ones:
| Prompt | Arguments | What it does |
|---|---|---|
read_page |
url, question (optional) |
Reads the page as Markdown and answers the question, or summarises the page. |
audit_page |
url, device (optional: mobile or desktop) |
A health report: Lighthouse scores, Core Web Vitals and console errors. |
compare_pages |
url_a, url_b, focus (optional) |
Two pages side by side: what each says and how each presents itself. |
The resource urlpipe://pricing holds the plans and what each operation costs, so an
agent can check a price before it spends credits.
initialize, tools/list, prompts/list and resources/list answer without a token,
so you can see all of this straight from the server:
curl -s https://urlpipe.dev/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
A first prompt
Using urlpipe with sync: true, read https://news.ycombinator.com as Markdown and list
the five top stories with their links. Then take a screenshot of the first story's page
and tell me what the page looks like.
What it doesn't do
URLpipe answers questions about one URL at a time. It doesn't crawl whole sites,
discover URLs, or reach localhost and private addresses — it fetches public pages
from its own servers. It follows each site's robots.txt by default.
Links
- MCP server overview
- MCP docs — tokens, scopes, limits
- HTTP API docs and OpenAPI spec
- Free tools — try every operation without an account
- Questions: contact@urlpipe.dev
Licensed under MIT: the configuration and documentation in this repository. The URLpipe service is covered by its terms.
URLpipe MCP questions
How do I add URLpipe MCP to Claude Code?
Run claude mcp add --transport http mcp https://urlpipe.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add URLpipe MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does URLpipe MCP provide?
It exposes 17 tools, including list_projects, get_usage, fetch_markdown, fetch_html, capture_screenshot.
How does URLpipe handle JavaScript-heavy sites like React or Vue?
URLpipe loads every page in a real Chrome browser first, ensuring the agent receives the fully rendered content rather than an empty shell.
Can I use URLpipe for free?
Yes, you get 1,000 free credits every month without needing a credit card, and cached results cost nothing.
Does URLpipe crawl entire websites?
No, it is designed to answer questions about one URL at a time and does not crawl whole sites or discover new URLs.
Where is the data processed?
All fetching, rendering, and storage operations are processed within the EU.