Developer · Local MCP server
Feedthrough
Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.feedthrough/feedthrough- Version
- 0.4.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-04
- Updated
- 2026-09-04
- Publisher
- feedthrough (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/feedthrough) · how
- Listed under
- Browser automation MCP servers
- Repository
- github.com/feedthrough/feedthrough
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @feedthrough/mcp | 0.4.0 | stdio |
How to connect Feedthrough
Feedthrough runs locally from a Node.js package published to the npm registry: @feedthrough/mcp version 0.4.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @feedthrough/mcp@0.4.0. It reads these environment variables: FEEDTHROUGH_PORT and FEEDTHROUGH_ALLOWED_HOST_SUFFIXES; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"feedthrough": {
"command": "npx",
"args": [
"-y",
"@feedthrough/mcp@0.4.0"
],
"env": {
"FEEDTHROUGH_PORT": "<value>",
"FEEDTHROUGH_ALLOWED_HOST_SUFFIXES": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Feedback Synthesis MCPSynthesize GitHub Issues, HN and App Store reviews into ranked pain clusters. Pay-per-call x402. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| FeedbacksVisual website feedback, screenshots and team discussion for coding assistants. Self-hosted. | Local · stdio |
| FeedKitRSS/Atom feed collection with 417 curated feeds. Python MCP server. | Local · stdio |
| FeedmyagentTechnology intelligence feed for AI agents: tech stack, compliance, security. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Feishu User PluginFeishu/Lark MCP server + CLI tool. 85 tools, 3 auth layers. Send as user via cookie+protobuf. | Local · stdio |
| Feldspar free repository security scanFree deterministic security scan of public git repos: OSV.dev vulnerable deps, secrets, config lint. | Remote · HTTPLive check: ✓ handshake |
| Fenestra MCPRender and verify native Rust GUIs headlessly: access tree, query, a11y, screenshots, motion. | Local · stdio |
| Feode MCPFEODE: AI-accessible precision machining & testing; offshore P&A, subsea wellhead, drill-pipe. | Remote · HTTPLive check: ✓ handshake |