Puter MCP
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse.
使っているAIアプリを選んで、設定をコピーしてください。
チェック 5/5 合格 · 質問内容は提供元のサーバー(urlpipe.dev)を通ります
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 5 分
URLpipe のキーが必要です(提供元のサイトで作成) · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
URLpipehttps://urlpipe.dev/mcpRequest headers に、この名前と値を追加
AuthorizationBearer <ここにキーを貼り付け>キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Authentication は Claude が検出したままにして Add を押します
+ConnectorsURLpipe
URLpipe を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が URLpipe を使っていると言うか、回答に URLpipe のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT はまだ URLpipe につなげません
URLpipe は接続時に自分のキーが必要ですが、OpenAI のヘルプページは OAuth ログインしか説明しておらず、確認できたキー入力方法がありません
A · URLpipe につなげるアプリを使う
Claude Code につなげます · 約 5 分
URLpipe のキーが必要です(提供元のサイトで作成)
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user urlpipe https://urlpipe.dev/mcp --header 'Authorization: Bearer {token}'Enter の前に「your-value」を自分のキーに書き換えてください
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
URLpipe が一覧にあり、接続済みと表示されれば OK です
URLpipe を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が URLpipe を使っていると言うか、回答に URLpipe のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 5 分
URLpipe のキーが必要です(提供元のサイトで作成)
URLpipe の設定で Authorization が空です。自分のキーを入れて保存します
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
URLpipe を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が URLpipe を使っていると言うか、回答に URLpipe のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 5 分
URLpipe のキーが必要です(提供元のサイトで作成)
URLpipe の設定で Authorization が空です。自分のキーを入れて保存します
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
URLpipe を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が URLpipe を使っていると言うか、回答に URLpipe のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code
claude mcp add --transport http --scope user urlpipe https://urlpipe.dev/mcp --header 'Authorization: Bearer {token}'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"urlpipe": {
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer {token}"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"urlpipe": {
"type": "http",
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer {token}"
}
}
}
}この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月8日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
list_projectsThe projects this token can reach, each with how many requests it has made in the last 30 days and where its results are delivered. Start here: every other tool takes a project_id from this list. A project is the unit a request is billed and recorded against — credits themselves
get_usageWhat the organization's plan allows, how much of it is left this period, and what each operation costs. Worth reading before a run of expensive calls: the operations differ by seventeen times in price, so the difference between fetch_markdown and summarize_page over a hundred pag
fetch_markdownExposes POST /markdown. Renders the page in headless Chrome and converts its main content to clean Markdown — headings, lists, links and code kept, navigation, sidebars and cookie banners dropped. Start here when you want to READ a page. It is the cheapest operation we sell (1 cr
fetch_htmlExposes POST /html. Returns the page's HTML after JavaScript has run and redirects have been followed — the DOM a real browser sees, not the empty shell curl returns. 1 credit. Use it when you need the markup itself: a specific attribute, a script tag, a structured-data block. If
capture_screenshotExposes POST /screenshot. Captures the whole rendered page as a PNG — JavaScript executed, web fonts and images included, exactly as a browser would draw it. 1 credit, whichever options you use. Use it to see a page rather than read it: layout, visual regressions, link previews,
capture_pdfExposes POST /pdf. Prints the whole rendered page to a PDF — JavaScript executed, web fonts and lazy-loaded images included, its headings as bookmarks. 1 credit, whichever options you use. Use it to archive or hand on a page as a document: a receipt, an article, a report, terms a
capture_console_errorsExposes POST /console. Loads the page in headless Chrome and returns what it reported through console.error and console.warn during load, plus uncaught exceptions and unhandled promise rejections (not console.log). 1 credit. What you would open DevTools for: broken third-party sc
run_lighthouse_auditExposes POST /lighthouse. Runs a real Google Lighthouse audit against the live page: performance, accessibility, best-practices and SEO scores plus Core Web Vitals. 2 credits — dearer than a page fetch because the audit runs in its own limited lane, so it also takes longer than a
extract_metadataExposes POST /meta. Reads everything a page declares about itself — Open Graph, Twitter cards, meta tags, JSON-LD, microdata and links — into one object with the same keys on every page: title, description, site name, kind of page, language, authors, publication and update dates,
detect_technologiesExposes POST /technologies. Detects what a page is built with — CMS, e-commerce platform, JavaScript frameworks and libraries, analytics and tag managers, advertising and marketing tools, CDN, web server, programming language, payment providers, chat widgets, consent managers and
extract_keywordsExposes POST /keywords. Returns the 5–15 terms and phrases that best represent the page, ordered by relevance — ranked by a language model, not by raw frequency. 15 credits. As with summarize_page: if you are going to reason over the result yourself, fetch_markdown costs 1 credit
summarize_pageExposes POST /summarize. Returns a concise Markdown summary of the page's main content, with the navigation, ads and boilerplate left out. The most expensive operation we sell, at 17 credits, because it runs a language model over the page. If YOU are the model that will read it,
extract_dataExposes POST /extract. Reads the page and fills an object YOU define: pass `fields`, each with a name, a type and a description of what to take from the page, and get back exactly those keys in that order. Anything the page does not give comes back null — values are never guessed
scrape_urlExposes POST /scrape. Runs any subset of the other operations in one request, served from a single page visit where possible. Each operation is billed and stored exactly as the individual call would be, so this is not a discount — with one exception, and it is the reason to use i
get_resultExposes GET /result/:token. Returns the result of a past request, in the same form the call that made it would have returned — Markdown as Markdown, a structured operation as its object, a screenshot as an image, a PDF as an embedded application/pdf resource, a scrape as its comb
list_requestsA project's recent requests, newest first, with each one's token. Look here before fetching a page: if somebody already pulled it, passing that token to get_result returns the same result for nothing. A /scrape appears as one entry — its per-operation children are internal, and t
get_requestEverything about one past request except its result: what was asked for, how long each stage took, whether it came from the store, and how the webhook delivery went. This is the metadata; get_result returns the page itself. Reach for this one when a call did not do what you expec
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月12日にチェック
レジストリ名はドメイン urlpipe.dev で確認済みです(レジストリがドメインの所有を確認しています)
コードの最終更新:30 日前
MITを使用
605ミリ秒で応答(HTTP 200)
サインイン不要
17件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:Authorization
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は30 日前、最新バージョン(1.4.0)がレジストリに届いたのは30 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP に対応したアプリでも使えます(例:ChatGPT Business 以上)。
同じカテゴリには:Puter MCP, XcodeBuildMCP, XcodeBuildMCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
URLpipe MCP server
Give your agent a browser that runs the page's JavaScript before it reads it.
Website · Docs · Pricing
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.
https://urlpipe.dev/mcp. Nothing to install or run.This repository holds the server's registry entry (server.json) and the setup for each client. The server itself runs at urlpipe.dev.
Every client sends it as Authorization: Bearer YOUR_TOKEN.
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}" } } } }
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/mcp.json, or .cursor/mcp.json in a project:
{
"mcpServers": { "urlpipe": { "url": "https://urlpipe.dev/mcp", "headers": { "Authorization": "Bearer ${env:URLPIPE_TOKEN}" } } } }
.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}" } } } }
mcp_config.json:
{
"mcpServers": { "urlpipe": { "serverUrl": "https://urlpipe.dev/mcp", "headers": { "Authorization": "Bearer ${env:URLPIPE_TOKEN}" } } } }
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"] } } }
settings.json:
{
"context_servers": { "urlpipe": { "url": "https://urlpipe.dev/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }
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.
| 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).
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"}'
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.
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.
Licensed under MIT: the configuration and documentation in this repository. The URLpipe service is covered by its terms.