Integrations

URLpipe in Cline

Let Cline look at the page it is building against — rendered, in a real browser.

By Roger Campos · Last updated: September 2026

TL;DR

Cline connects to remote MCP servers from cline_mcp_settings.json. Add URLpipe with "type": "streamableHttp", "url": "https://urlpipe.dev/mcp" and an Authorization header; the Remote Servers tab can add the URL, but headers go in the JSON. Cline then has fourteen tools to read, render and screenshot pages.

Start free See the API

Free plan, no credit card. 1,000 credits a month.

Why

What Cline gets

Cline works step by step and asks before it acts, which suits a tool that spends credits. URLpipe gives it fetch_html for the rendered DOM — the markup after JavaScript ran, for writing scrapers, tests and selectors against the real thing — capture_screenshot to see the result, and fetch_markdown to read.

Setup

1. Create an organization token

MCP uses its own credential, not a project API key: an organization token, created under Organization → MCP access in the dashboard. An agent works across projects, and a project key names only one. The token is shown once — copy it when you create it.

Choose Fetch pages and read results for an agent that works normally, or Read past results only for one that must not spend credits (more on that below). The account's email address must be confirmed before the token works; until then the server answers 403 with email_unverified.

Setup

2. Add the server to Cline

Click the MCP Servers icon at the top of the Cline panel, open the Configure tab, and choose Configure MCP Servers to open cline_mcp_settings.json. The Remote Servers tab can add a name and URL, but custom headers are set in this file.

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"]
    }
  }
}

streamableHttp is the transport URLpipe serves. autoApprove lists tools Cline may call without asking: the three above cost nothing, while the fetching tools spend credits, so leaving those to a confirmation keeps you in the loop. The file sits in the extension's own storage, outside your repository.

Check it connected

Back in MCP Servers, urlpipe is listed with its tools and an enable toggle. Expand it to see the fourteen tools; if the list is empty, the header is the usual suspect. Then ask Cline to call list_projects — it is free and proves the token works.

Try it

3. A first prompt to try

Prompt for Cline

Use urlpipe fetch_html with sync: true on https://example.com/products and write a
Playwright test in tests/products.spec.ts that checks every product card has a name, a
price and an image. Take a screenshot afterwards so I can see the page you tested.

Rendered HTML is the DOM after scripts ran — the thing a test actually runs against — and costs 1 credit.

The agent starts with list_projects, because every fetching tool takes a project_id. Async is the default, as over HTTP: without sync: true a tool returns a token and the agent collects the result with get_result. Most agents work this out from the tool descriptions; saying "use sync: true" in the prompt saves a round trip.

Tokens

Keep the token safe and the spend bounded

A read-only token cannot spend. Created with Read past results only, it can list projects, read usage and retrieve results already paid for, and nothing else. Give it to an agent that should only look things up.
Narrow it. A token can be limited to one project, or given an expiry date. Deleting it revokes it at once.
Keep it out of version control. Put it in an environment variable or the client's secret prompt rather than in a config file you commit.
Same credits as the API. fetch_markdown costs 1 credit, summarize_page 17; a cached result is free. get_usage shows what is left. See pricing.

Troubleshooting

If it doesn't connect

401 — "A bearer token is required" or "not valid". The header must be exactly Authorization: Bearer YOUR_TOKEN: the word Bearer, one space, the token. Check that an environment variable actually expanded.
403 email_unverified. Confirm the account's email address; the token then works as it is.
The client asks you to sign in with OAuth. URLpipe has no OAuth flow — the header is the whole of the authentication. Set it, and the client has nothing to sign in to.
Tool calls fail with rate_limited. The server allows 300 calls per 5 minutes per token. concurrency_limit means your plan's parallel requests are all busy.
Cline tries SSE. Make sure type is streamableHttp; URLpipe serves no SSE stream.

The server speaks streamable HTTP and answers each message with a single JSON response — it opens no SSE stream and keeps no session. Every argument and tool is in the MCP docs.

Endpoints

The endpoints on this page

/html API docs /screenshot API docs

FAQ

Frequently asked questions

Can I add custom headers in Cline's Remote Servers tab?

No — headers are set in cline_mcp_settings.json. The tab adds the name, URL and transport; open the file from Configure MCP Servers to add the Authorization header.

Which transport should Cline use for URLpipe?

streamableHttp. URLpipe answers each message with one JSON response and serves no SSE stream.

Which tools are safe to auto-approve?

list_projects, get_usage and get_result spend nothing. Every fetching tool spends credits, so it is sensible to keep those behind Cline's confirmation.

What is the difference between fetch_html and fetch_markdown?

fetch_html returns the serialized rendered DOM; fetch_markdown converts that DOM to Markdown with navigation and chrome dropped. Both cost 1 credit.

Keep reading

Archiving pages as screenshots Why we built our own rendering engine networkidle Headless browser MCP server Claude Desktop All of integrations

Connect it in five minutes.

Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.

Start free Email the team