Feedthrough MCP Server
Debug with AI - from inside your app. Feedthrough injects a lightweight debug bridge into any running web page, then exposes everything - DOM state, console logs, network requests, and user interactions - as MCP tools. Any MCP-compatible AI agent can inspect and drive the page conversationally, in real time. It runs locally over stdio via the published package.
People connecting browser automation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.
VERIFIED ACTIVE
LAST COMMIT 2026-06-16 · ★ 4 · #120 OF 196 MAINTAINED BROWSER AUTOMATION · VERIFIED 2026-08-25
MIT · TypeScript servers · how we verify → /methodology
01 · Install Feedthrough
before you install - you'll need
The README does not document required environment variables for a basic install.
Claude Code
claude mcp add feedthrough-feedthrough -- npx -y @feedthrough/mcp Claude Desktop / Cursor / VS Code - add to config
{
"mcpServers": {
"feedthrough-feedthrough": {
"command": "npx",
"args": [
"-y",
"@feedthrough/mcp"
]
}
}
} Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.
Using another client? Same JSON, different key
Claude Desktop · mcpServers
Cursor · mcpServers
VS Code · servers
Windsurf · mcpServers
Zed · context_servers
Cline · mcpServers
Roo Code · mcpServers
Continue · mcpServers
LibreChat · mcpServers
Gemini CLI · mcpServers
Codex CLI · mcp_servers
Full setup guides: every client.
02 · Evidence
Security posture
What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.
runs as local process (stdio) - runs on your machine with your user's permissions
license MIT - declared in the repository
npm package @feedthrough/mcp - published under the repo owner's npm scope (@feedthrough)
registry namespace io.github.feedthrough is GitHub-verified and matches the repo owner
03 · What Feedthrough can do
Prose above is summarized from the project's README and registry record - no invented capabilities.
Latest releases
v0.3.2 · 2026-06-16
Tighten occlusion demo + untrack generated .astro files · Remove the MCP server Dockerfile and its CI job · Improve tool and parameter documentation
v0.3.1 · 2026-06-07
add repository metadata so 0.3.0 publishes with provenance · add glama.json for Glama MCP listing ownership · add occlusion landing-page clip · non-obvious tool uses in get_instructions (+ v0.3.1)
v0.3.0 · 2026-06-07
Shorten server.json description to registry's 100-char limit · Make MCP registry publish idempotent and retryable · 0.3: inspect_element enhancements, Biome, version bump
04 · Who maintains Feedthrough
feedthrough is maintained by feedthrough. It's the only MCP server we track from this author; the repo dates to May 2026.
05 · Facts
- repository
- github.com/feedthrough/feedthrough
- category
- browser automation - ranked #120 of 196 actively-maintained browser automation servers as of 2026-08-25.
- release cadence
- 5 releases in the last 90 days (latest 2026-06-16)
- registry
- io.github.feedthrough/feedthrough (active, first published 2026-06-05 · 4 versions)
- packages
- npm:@feedthrough/mcp
06 · Feedthrough FAQ
What is Feedthrough?
Debug with AI - from inside your app. Feedthrough injects a lightweight debug bridge into any running web page, then exposes everything - DOM state, console logs, network requests, and user interactions - as MCP tools. Any MCP-compatible AI agent can inspect and drive the page conversationally, in real time. It runs locally over stdio via the published package.
Is Feedthrough still maintained?
Yes - as of 2026-08-25, its last commit was 2026-06-16 and it shipped 5 releases in the last 90 days. We re-verify nightly.
How do I install Feedthrough?
Run `npx -y @feedthrough/mcp`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.
Does Feedthrough run locally?
Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.
07 · Alternatives to Feedthrough
Alternatives to Feedthrough
Maintained browser automation servers if Feedthrough isn't the fit.
- Chrome DevTools MCP MCP server for Chrome DevTools ★ 49,617 · 2026-08-23
- Server Browser MCP server for browser use access ★ 38,704 · 2026-08-05
- Playwright MCP Playwright Tools for MCP ★ 36,436 · 2026-08-21
- Mobile MCP MCP server for iOS and Android Mobile Development, Automation and Testing ★ 5,995 · 2026-08-18
- Agent Device (callstack) MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps ★ 4,212 · 2026-08-24
- Agent Device (callstackincubator) Let AI agents inspect, control, and debug real iOS, Android, desktop, and TV apps ★ 4,211 · 2026-08-24
Pairs well with
Servers that cover what Feedthrough doesn't - only shown when the pairing reason fits the companion.
- Firecrawl MCP Server → web scraping companion web scraping · ★ 7,310
- Tavily MCP → web scraping companion web scraping · ★ 2,351
- Codebase Memory → memory companion memory · ★ 40,198
- Memorix → memory companion memory · ★ 688
- Server Filesystem → filesystem companion filesystem · ★ 38,704
- X402 List MCP → filesystem companion filesystem · ★ 58
More browser automation MCP servers · Scout · Flyto Core · Expo Android MCP · Chrome Bridge · Deepadb
More TypeScript MCP servers · Figma To Code MCP · Bibelstudium MCP · File To PDF · Spectra MCP Server · Mermaid MCP App · see all