MCP server de URLpipe
Commit 12 oct 2026Permite que un agente de IA renderice páginas web con mucho JavaScript para extraer Markdown, capturas de pantalla, PDFs, metadatos y auditorías de Lighthouse.
También conocido como URLpipe/mcp, mcp
- Stars
- 0
- Herramientas
- 17
- Descargas, 30 días
- —
- Última versión
- 1.4.0
- Último commit
- 12 oct 2026
- Licencia
- MIT
¿Qué es URLpipe MCP?
Permite que un agente de IA renderice páginas web con mucho JavaScript para extraer Markdown, capturas de pantalla, PDFs, metadatos y auditorías de Lighthouse. Expone 17 herramientas, como list_projects, get_usage, fetch_markdown.
Resumen generado a partir del README del proyecto
Acerca del MCP server de URLpipe
URLpipe ofrece un MCP server alojado que permite a los agentes de IA interactuar con sitios web modernos con mucho JavaScript. A diferencia de las herramientas de fetch estándar que solo recuperan una estructura HTML vacía de aplicaciones React o Vue, este servidor utiliza una instancia real de Chrome para renderizar las páginas por completo antes de procesarlas. Esto permite que los agentes vean exactamente lo mismo que un usuario humano en un navegador.
Se accede al servicio a través de una conexión streamable HTTP en urlpipe.dev/mcp, lo que lo hace compatible con clientes como Claude Desktop, Cursor, VS Code y Windsurf. Los usuarios se conectan proporcionando un bearer token obtenido desde el dashboard de URLpipe. El servidor incluye 17 herramientas diferentes para diversas tareas, como obtener contenido en Markdown, capturar capturas de pantalla, generar PDFs y ejecutar auditorías de Lighthouse para rendimiento y SEO.
El procesamiento y almacenamiento de datos ocurre dentro de la UE. El sistema opera bajo un modelo basado en créditos donde los usuarios reciben 1,000 créditos gratuitos cada mes. Para gestionar los costos, el servidor admite resultados en caché que no consumen créditos, y los usuarios pueden elegir entre solicitudes asíncronas o usar el parámetro sync para esperar un resultado.
Qué puedes hacer con él
- 1Extraer contenido de sitios dinámicosUn agente puede leer el contenido principal de un dashboard de React o Vue convirtiendo la página renderizada en un Markdown limpio.
- 2Realizar auditorías de rendimiento webUn desarrollador puede solicitar un informe de salud completo que incluya puntuaciones de Lighthouse y Core Web Vitals para una URL específica.
- 3Capturar representaciones visuales de páginasUna IA puede tomar una captura de pantalla de toda la página o generar un PDF para inspeccionar visualmente el diseño de un sitio web.
- 4Scrapear datos estructurados de páginas webPuedes instruir a un agente para que extraiga detalles específicos de productos o precios hacia un esquema personalizado.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar URLpipe MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar URLpipe MCP en Claude Code
$ claude mcp add --transport http mcp https://urlpipe.dev/mcpInstalar URLpipe MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://urlpipe.dev/mcp"
}
}
}Instalar URLpipe MCP en VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://urlpipe.dev/mcp"
}
}
}Instalar URLpipe MCP en VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://urlpipe.dev/mcp"}'Instalar URLpipe MCP en Codex
$ codex mcp add mcp --url https://urlpipe.dev/mcpInstalar URLpipe MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] url = "https://urlpipe.dev/mcp"
Instalar URLpipe MCP en Gemini CLI
$ gemini mcp add -s user --transport http mcp https://urlpipe.dev/mcpInstalar URLpipe MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://urlpipe.dev/mcp",
"type": "http"
}
}
}Herramientas de URLpipe MCP 17
Detectado desde el 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 | — |
Mostrar las 17 herramientasMostrar menos herramientas
extract_datascrape_urlget_resultlist_requestsget_request
| extract_data | — | |
| scrape_url | — | |
| get_result | — | |
| list_requests | — | |
| get_request | — |
Configuración
URLPIPE_AUTH
| Nombre | Descripción | Tipo |
|---|---|---|
| URLPIPE_AUTH | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesibleurlpipe/mcp is public and reachablegithub.com/urlpipe/mcp ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-12github.com/urlpipe/mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPinitialize answered with protocol 2025-06-18 in 121 msAprobado
README
Ver en 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.
Preguntas sobre URLpipe MCP
¿Cómo agrego URLpipe MCP a Claude Code?
Ejecuta claude mcp add --transport http mcp https://urlpipe.dev/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego URLpipe MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona URLpipe MCP?
Expone 17 herramientas, incluidas list_projects, get_usage, fetch_markdown, fetch_html, capture_screenshot.
¿Cómo maneja URLpipe los sitios con mucho JavaScript como React o Vue?
URLpipe carga cada página primero en un navegador Chrome real, asegurando que el agente reciba el contenido completamente renderizado en lugar de una estructura HTML vacía.
¿Puedo usar URLpipe gratis?
Sí, recibes 1,000 créditos gratuitos cada mes sin necesidad de una tarjeta de crédito, y los resultados en caché no tienen costo.
¿URLpipe rastrea sitios web completos?
No, está diseñado para responder preguntas sobre una URL a la vez y no rastrea sitios enteros ni descubre nuevas URLs.
¿Dónde se procesan los datos?
Todas las operaciones de obtención, renderizado y almacenamiento se procesan dentro de la UE.