Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.
Connect Runs on your machine
claude mcp add feedthrough -e FEEDTHROUGH_PORT=<FEEDTHROUGH_PORT> -e FEEDTHROUGH_ALLOWED_HOST_SUFFIXES=<FEEDTHROUGH_ALLOWED_HOST_SUFFIXES> -- npx -y @feedthrough/[email protected]{
"mcpServers": {
"feedthrough": {
"command": "npx",
"args": [
"-y",
"@feedthrough/[email protected]"
],
"env": {
"FEEDTHROUGH_PORT": "<FEEDTHROUGH_PORT>",
"FEEDTHROUGH_ALLOWED_HOST_SUFFIXES": "<FEEDTHROUGH_ALLOWED_HOST_SUFFIXES>"
}
}
}
}{
"mcpServers": {
"feedthrough": {
"command": "npx",
"args": [
"-y",
"@feedthrough/[email protected]"
],
"env": {
"FEEDTHROUGH_PORT": "<FEEDTHROUGH_PORT>",
"FEEDTHROUGH_ALLOWED_HOST_SUFFIXES": "<FEEDTHROUGH_ALLOWED_HOST_SUFFIXES>"
}
}
}
}{
"servers": {
"feedthrough": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@feedthrough/[email protected]"
],
"env": {
"FEEDTHROUGH_PORT": "<FEEDTHROUGH_PORT>",
"FEEDTHROUGH_ALLOWED_HOST_SUFFIXES": "<FEEDTHROUGH_ALLOWED_HOST_SUFFIXES>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
FEEDTHROUGH_PORTOptional | Port the bridge WebSocket server listens on (defaults to 8765). |
FEEDTHROUGH_ALLOWED_HOST_SUFFIXESOptional | Comma-separated non-loopback host suffixes allowed to connect (defaults to .test). Setting it replaces the default, so include .test to keep it. |
Details
| Package | @feedthrough/[email protected] (NPM, stdio) |
| First published | 4 Sep 2026 |
| Last updated | 4 Sep 2026 |
| Registry name | io.github.feedthrough/feedthrough |
More browser automation servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.