URLpipe

A 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

1. Sign up and confirm your email address.
2. 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.
3. 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

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:

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: [email protected]

Licensed under MIT: the configuration and documentation in this repository. The URLpipe service is covered by its terms.