Browser-native tool injection bridges the MCP gap for internal SaaS
u/schequm describes a browser-based approach where an AI agent dynamically writes and registers JavaScript tools directly into a live page tab, bypassing the need for a dedicated MCP server for SaaS tools that have no public API.
Score breakdown
The post highlights a structural gap in the MCP ecosystem — the long tail of internal and niche SaaS tools that will never ship a dedicated server — and describes a browser-native injection pattern as a lightweight alternative to both vision-based agent loops and full MCP server deployments.
- 01AI agents with MCP servers for GitHub, Linear, and Postgres still stall on SaaS tools that have no public API or MCP server.
- 02The fallback — screenshot-click loops — costs roughly a thousand tokens per image and a full inference per step.
- 03The proposed pattern has the agent inject a JS tool directly into the browser tab via a `registerTool` call, with no server or build step required.
u/schequm on r/mcp outlines a problem that surfaces repeatedly when using AI agents against the long tail of SaaS tools: popular services like GitHub, Linear, and Postgres have MCP servers, but many paid SaaS products have no public API and no MCP server. Without a structured interface, agents fall back to vision-based interaction — taking screenshots, guessing at UI state, clicking, and re-checking — a loop the post characterizes as consuming roughly a thousand tokens per image and a full inference per step, turning a thirty-second manual task into a ten-minute agent ordeal.
The alternative the post describes is a browser-native tool injection pattern.
The alternative the post describes is a browser-native tool injection pattern. Rather than writing a standalone Playwright script (which must be rewritten and rerun whenever the page behaves unexpectedly), the agent writes a JavaScript tool directly into the live tab using a `registerTool` call. The tool is immediately callable by name, accepts JSON input, and returns JSON output, with round-trips in the 50–100 ms range. Because tools live on the tab, the agent's context only carries tools relevant to the page currently open. A key step is an initial "probe" phase: the agent temporarily hooks the page's own `fetch` calls to read back the endpoints and payloads the site's frontend is already making to its own backend — eliminating the need for the user to manually copy requests out of DevTools. The probe is then discarded and replaced by the real tool.
The author discloses they built this capability into a product called Customaise, which they describe as "Tampermonkey for AI agents." It is offered free, with paid tiers for high-volume usage. The post closes with an open question to the community about where the practical line sits between standing up a full MCP server versus reaching for a quick browser-side page tool.
Key facts
- 01AI agents with MCP servers for GitHub, Linear, and Postgres still stall on SaaS tools that have no public API or MCP server.
- 02The fallback — screenshot-click loops — costs roughly a thousand tokens per image and a full inference per step.
- 03The proposed pattern has the agent inject a JS tool directly into the browser tab via a `registerTool` call, with no server or build step required.
- 04A throwaway 'probe' script hooks the page's own `fetch` calls to discover the endpoints and payloads the site already uses internally.
- 05The probe is discarded after discovery; the real tool replays those requests in the user's existing authenticated session.
- 06Tool round-trips run in the 50–100 ms range, and tools live only on the relevant tab so they don't bloat the agent's context.
- 07The author built this into a product called Customaise, described as 'Tampermonkey for AI agents,' free with paid tiers for heavy usage.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 9, 2026 · 17:05 UTC. How this works →