MCP.Market

Feedthrough MCP server

by feedthrough·io.github.feedthrough/feedthrough·v0.4.0·4 stars
No reviews yet

Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.

A86/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

4 stars109 downloads/wk

Reviews

Write one

Nobody has reviewed Feedthrough yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Feedthrough tools (16)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • click

    Click an element by calling its native click(), which fires a click event and runs the

  • connection_status

    Check whether a browser with the Feedthrough bridge is currently connected.

  • fill

    Set the value of an input, textarea, or select element. Focuses the element, assigns the

  • get_console_logs

    Return console output captured since the bridge connected. Covers every console method —

  • get_html

    Return the outerHTML of an element (capped at 50 KB). Use this when the summarised query_dom

  • get_instructions

    Returns the Feedthrough usage guide as a Markdown text document, with sections for the

  • get_network_requests

    Return all fetch and XHR requests captured since the bridge connected, including URL, method,

  • get_page_info

    Return basic page context: current URL, document title, readyState, viewport size, scroll

  • hover

    Hover over an element by dispatching synthetic, bubbling mouseover and mouseenter events

  • inspect_element

    Return full details about a single element: tag, id, classes, all attributes, text content,

  • press_key

    Dispatch a key press (keydown/keypress/keyup) on an element — e.g. Enter to submit a search,

  • query_dom

    Query the page with a CSS selector and return a summary of every matching element

  • reset_overrides

    Undo every set_style / set_attribute / set_text change the bridge has applied since it

  • set_attribute

    Set or remove an attribute on an element to preview a change (toggle disabled, swap a class,

  • set_style

    Set one or more inline CSS properties on an element to PREVIEW a visual change live (e.g.

  • set_text

    Replace an element's text content to preview wording/label changes. Live preview only — not

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan9 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 42 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Feedthrough compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 67% of 867 Scraping and browsing servers
Tools
16
the typical Scraping and browsing server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
4
more than 72% of 584 Scraping and browsing servers
Downloads a week
109
more than 57% of 312 Scraping and browsing servers with a package

What its tools let an agent do: 13 read · 3 change

Install Feedthrough in Claude Code, Cursor or VS Code

Runs npx -y @feedthrough/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add feedthrough -- npx -y @feedthrough/mcp
Add to Cursor

What the publisher says

From the Feedthrough repository's README, as published. We do not edit it. Read it on GitHub

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.

Browser (any)
 └── @feedthrough/core          ← injected into your page
      ├── console interceptor
      ├── fetch / XHR interceptor
      └── DOM inspector
      ↕  WebSocket
@feedthrough/mcp               ← MCP server, exposes tools over stdio
 └── Tools: click, fill, inspect_element, query_dom,
            get_console_logs, get_network_requests, …
      ↕  MCP protocol
Claude Code / Cursor / any MCP client

The name

Many physics and chemistry experiments run inside a sealed vacuum chamber, with all the air pumped out so nothing contaminates the experiment. The catch: you still need to control instruments inside the chamber and read their measurements, and the smallest air leak ruins the run. A feedthrough is the part that solves this — a specially engineered connector that carries electrical signals through the chamber wall while keeping the vacuum perfectly intact. You can't reach inside, but the feedthrough lets you observe and control what's happening in there anyway.

The parallel is exact: Feedthrough extracts runtime debug data from inside a running web app without disturbing it, and sends control signals back in — clicks, keystrokes, DOM queries — without breaking the execution environment.

Why Feedthrough?

Every other browser MCP tool is an external observer — it controls the browser from outside via Puppeteer or CDP and only works in Chrome. Feedthrough is an embedded agent. It runs inside the page, so it sees:

  • Framework internals (React component trees, Redux store, custom globals)
  • Any browser, not just Chrome
  • Your existing dev workflow — no separate controlled browser to launch
  • Cypress's own browser context during test runs

Packages

Framework support

Quick start

1. Start the MCP server

npx @feedthrough/mcp

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Feedthrough: common questions

Is Feedthrough MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the Feedthrough safety report
How do I install Feedthrough?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Feedthrough need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Feedthrough maintained?
The last commit was 62 days ago (2026-09-04). The latest release is v0.4.0.
What can I use instead of Feedthrough?
Servers from other publishers that do the same job: Web Browser (kogiQA) MCP server, SeleniumBase MCP server and AIHawk MCP server. Compare all Feedthrough alternatives.
How does Feedthrough compare with other Scraping and browsing MCP servers?
safety score 86/100 (higher than 67% of 867 Scraping and browsing servers); tools 16 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Feedthrough

Same job from other publishers: the closest match first, then the best rated.

All Feedthrough alternatives →
  • Web Browser (kogiQA)
    This web browser has been designed to help your agent debug and develop complex web applications.
    C
  • SeleniumBase MCP
    Stealthy browser automation, testing, and web-scraping via CDP Mode.
    A
  • AIHawk
    AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
    More from feder-cr →
    A
  • Browser Use
    Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
    A
  • CloakBrowser MCP
    Playwright MCP-compatible browser automation bridge for CloakBrowser Chromium.
    B