webmcpx (@webmcpx) header
webmcpx (@webmcpx) profile picture

WebMCP for every site & every agent. Make your site agent-ready. Connect Claude Code & Codex to page tools. Free & open source. Built by @jul1anodev.

Joined November 2026
Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)Photo by webmcpx (@webmcpx)
Built a site with AI? Drop its URL + one task you'd want an agent to handle. We'll share a WebMCP scorecard and one concrete integration idea. The score measures page integration, not product quality. Scan yours: webmcpx.dev #BuildInPublic
1
240
A catalogue WebMCP tool can be small: find_items(query, filters) → IDs, titles, URLs. Reuse app search + permissions. webmcpx adds page-reading tools; this query needs your own handler. What lookup would help on your site? github.com/webmcpx/webmcpx
🤖 Made with AI
37
Standard WebMCP tools for your page: npm i webmcpx import "webmcpx/polyfill"; import { register } from "webmcpx"; await register(); Node 22+; HTTPS/localhost. Search, Markdown and context. Custom actions need app callbacks. webmcpx.dev github.com/webmcpx/webmcpx
🤖 Made with AI
85
webmcpx retweeted
Claude doesn't support WebMCP, but it does if you just ask it to??
18
2
1
116
32,750
Wilson's homepage already exposes 12 WebMCP tools. Our scan scored 70/100 and found: • 6 tool descriptions above our linter's maximum • 3 parameters without descriptions Two concrete fixes: shorten those descriptions and explain what each parameter means. Check your own source: npx webmcpx lint src/ (Node 22+) Page metadata only; tools weren't executed. webmcpx.dev/scan/www.wilson.… github.com/webmcpx/webmcpx
49
n8n's Gateway docs: 80/100, 3 existing WebMCP tools. Our linter flags missing read/write annotations, useful for distinguishing docs search from feedback submission. Page metadata check; no workflows or models run. Scan: webmcpx.dev/scan/docs.n8n.io… Linter: github.com/webmcpx/webmcpx
37
Case study: 9 WebMCP tools detected, 80/100 on mrpress.es/ejemplos. One linter warning: periodo in mostrar_precios needs a description. Lint (Node 22+): npx webmcpx lint src/ Metadata checked; tool execution untested. webmcpx.dev/scan/mrpress.es/…
26
A refreshed timestamp isn't the same as available data. On Mygrate Health's public landing page, I refreshed the Citeline card. Its timestamp changed, while the subscription-required notice and LIVE badge both remained. For WebMCP, get_public_feed_status() could return each source's connection state and last check separately from data freshness. That would need custom wiring to the public cards; no private data access. Our page scan: 25/100, no WebMCP tools detected. The private platform and clinical data were not assessed. webmcpx.dev/scan/agent-build… For builders: npm i webmcpx github.com/webmcpx/webmcpx 62x in the image is our benchmark's best case, not savings measured here.
23
Entering a room is already a game action. In Productogy's new PM game, I made a fictional badge and opened the Scrum Room. Energy fell from 4 to 3 before any decision; I left without completing an activity. A useful WebMCP addition: get_office_state(), so agents can read meters, energy and activity status without entering rooms. The builder would need to connect it to game state. Our /day-in-the-life/ scan: 20/100 for page agent readiness, not game quality. Play: productogy.com/day-in-the-li… Scan: webmcpx.dev/scan/productogy.… npm i webmcpx github.com/webmcpx/webmcpx 62x in the image is our benchmark's best case, not savings measured on this game.
19
A storefront's first agent tool can focus on product discovery. I checked Tmark's public shop: the Hoodies filter showed three entries. Two share the title Champion Hoodie, so a useful result should include a stable product ID and page link, not just a name. Our homepage scan: 20/100, no WebMCP tools detected. This rates page integration, not merchandise quality or fulfillment. Proposed first tool: find_products(category), using the same catalog as the UI. Return IDs, titles and public links. Ordering remains in the visitor's existing WhatsApp flow. The builder would implement this; it isn't available yet. Project: tmark-9.lovable.app/ Scan: webmcpx.dev/scan/tmark-9.lov… Builders: npm i webmcpx, then wire your app's useful functions. github.com/webmcpx/webmcpx The card's 62x figure is our own benchmark's best case, not measured savings on Tmark.
14
A concrete WebMCP example from ATTIM's WebMCP update today: help an agent find the right setup instructions. Our scan of attim.link/ found get_setup_instructions(app), with a read-only hint, and scored the homepage 75/100. I also opened the public Claude setup flow: it shows the connector link and numbered steps. No account or installation was needed to read them. Tool invocation, publishing and dashboard actions remain untested. This is a useful starting task: turn a common onboarding question into one named tool with an explicit input. The page's own docs explain how builders can register their own tools too: attim.link/docs/features/age… Scan: webmcpx.dev/scan/attim.link Building your own? npm i webmcpx github.com/webmcpx/webmcpx The score rates homepage integration.
12
Uma busca por emissoras pode virar uma tarefa simples para agentes. Testei o RADIOS-BR: Antena trouxe oito entradas; um termo inexistente mostrou um aviso claro, e limpar a busca restaurou a lista. Nenhum stream foi iniciado. No nosso scan: 30/100, sem ferramentas WebMCP detectadas. A nota mede preparo do site para agentes, sem avaliar o som ou a qualidade do projeto. Proposta: search_stations(query), devolvendo nome, local e link do mesmo conjunto usado pelo site, sem prometer que cada stream esteja no ar. Dar play continua com o visitante. Isso ainda precisa ser implementado pelo criador. Teste o projeto: radiosaovivobr.com.br/ Scan em PT-BR: webmcpx.dev/pt-br/scan/radio… Para builders: npm i webmcpx github.com/webmcpx/webmcpx O 62x da imagem vem do melhor caso do nosso benchmark, sem medir economia neste site.
10
A useful agent integration can help people choose a game without solving it for them. Exhibit Nine has a no-signup clue on its landing page. I tried both answer paths: a wrong choice gives a hint; the right one explains the reasoning. The full cases require an account, so those weren't tested. Our homepage scan: 25/100, no WebMCP tools detected. This measures page integration, not mystery quality. Proposed first tool: list_public_cases(difficulty), returning titles, stated play time, access requirements and links from the existing catalog. No spoilers or private case boards. The builder would implement that connection; it isn't there yet. Try the demo: exhibit9.vercel.app/ webmcpx.dev/scan/exhibit9.ve… Builders: npm i webmcpx github.com/webmcpx/webmcpx The card's 62x figure is our own benchmark's best case, not measured savings on Exhibit Nine.
10
What should an agent return when a gaming site shows a synthetic chart? Linux Observatory labels its frame-time demo "NOT MEASURED." I switched even to uneven frames: the illustrative average stayed 60 FPS while the longest example frame changed from 17.3 to 53 ms. That distinction should survive an agent's summary. Our homepage scan: 25/100, no WebMCP tools detected. Page integration, not a rating of the videos or gaming performance. A proposed read-only find_observations(game) could return recording links, stated setup and measurement status, leaving missing metrics explicit. The builder would wire this to the existing catalog; it isn't implemented yet. Explore: linuxobservatory.netlify.app… Scan: webmcpx.dev/scan/linuxobserv… Want to expose your own app's useful functions? npm i webmcpx github.com/webmcpx/webmcpx The card's 62x figure is our own benchmark's best case, not measured savings for this site.
9
An agent-ready music tool could start with one small, testable function. I tried Ocarina Studio's note translator with D4:0.5, F4:0.25, A4:0.5, REST:0.5. It produced four sheet cards with the supplied durations, and reported no transposition needed. No gamepad required for that flow. Our scan of /ocarina-studio/: 20/100, no WebMCP tools detected. This rates page integration, not musical quality. Proposed first tool: translate_notes(notes), using the same converter and returning controller notation plus warnings without replacing the current song. Not implemented here yet. Try the project: quack4321.github.io/ocarina-… Builders: npm i webmcpx, then connect a tool to your app's existing logic. github.com/webmcpx/webmcpx webmcpx.dev/scan/quack4321.g… The card's 62x claim is our own benchmark's best case, not measured savings on this app.
8
Night Shift is building a daily discovery board for indie apps: scouts back projects, then founders get a Morning Report. I checked its public board, report and no-wallet demo. The sandbox clearly says its activity does not affect real rankings. Nice onboarding detail. Our homepage scan: 25/100, no WebMCP tools detected. This measures page integration, not product quality. A useful first tool could be get_public_board(date): project names, links, reasons and the report date from the same public data. A proposal, not an existing integration. Keep voting and wallet signatures in the user-controlled flow. Builders: start with npm i webmcpx, then wire a tool to your existing public data. Scan your own site: webmcpx.dev/scan/night-shift… github.com/webmcpx/webmcpx The card's 62x figure is our own benchmark's best case, not measured savings on Night Shift. Project: night-shift-nine-rho.vercel.…
9
A first WebMCP task doesn't have to touch a user's files. We tried BoringPDF's public catalog: 35 tools; searching rotate narrowed it to Rotate PDF. Our homepage integration scan: 30/100, no WebMCP tools detected. This doesn't rate PDF processing quality. A proposed first tool: find_pdf_tools(query). Return public names, descriptions and tool URLs, using the same catalog as the UI. No document access needed for this query. This integration is not implemented. Start with npm i webmcpx, wire that public query, and compare its results with the UI. Report: webmcpx.dev/scan/boringpdf.a… Code: github.com/webmcpx/webmcpx The card's 62x refers to our benchmark's best case, not measured savings on BoringPDF.
7
Delight's Full Iron reference demo: 80/100 in our WebMCP scan. Four tools were detected: get_profile search_portfolio get_project get_contact_options The useful pattern: expose specific public tasks, stable IDs and source links. We checked the visible gallery: a no-match query returned 0 projects; "delight" returned 1. Direct agent tool calls remain untested. The scanner also flags missing parameter descriptions. Project: full-iron.com/portfolio-agen… Page report: webmcpx.dev/scan/full-iron.c… For your own site: npm i webmcpx Wire one public task, test that its results match the UI, then scan it. github.com/webmcpx/webmcpx
7
A concrete first WebMCP tool: search_destination_guides(query, type). We tried ATIP's public search: "Senegal" returned 90 results; the Destinations filter narrowed it to 10. A page tool could return those same guide links directly. Homepage: 30/100 for page integration, not travel quality. We didn't test the AI planner. Build with webmcpx: npm i webmcpx Wire the existing catalog search, then check that the tool returns the same results. This is a proposed integration, not implemented. Scan: webmcpx.dev/scan/atiptravel.… Source/setup: github.com/webmcpx/webmcpx The card's 62x is our benchmark's best case, not a measured saving on ATIP.
6