Snapstack Server runs on your own machine — the client starts it, so there is no endpoint to ping. 53 installs a week from npm. Last commit 15 Jun 2026.
Local always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1.
We read the source, 21 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, [config.dir], { detached: true, stdio: 'ignore' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add snapstack-server -- npx -y snapstack-server
{
"mcpServers": {
"snapstack-server": {
"args": [
"-y",
"snapstack-server"
],
"command": "npx"
}
}
}
[mcp_servers.snapstack-server]
command = "npx"
args = ["-y", "snapstack-server"]
{
"mcpServers": {
"snapstack-server": {
"args": [
"-y",
"snapstack-server"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"snapstack-server": {
"args": [
"-y",
"snapstack-server"
],
"command": "npx"
}
}
}
Real signed-browser automation for AI agents, over a local stdio MCP server.
BrowserStack's Official MCP Server
MCP server that bridges local apps with Selenix for browser automation.
MCP server for browser use access
MCP server for browser automation with AI agent
MCP server for browser automation via Vercel's agent-browser CLI
MCP server for Zen Browser automation via WebDriver BiDi
Local browser automation for MCP clients powered by DrissionPage.
Answers built from our own checks of this server.