@squidlerio/mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@squidlerio/squidler-mcp
MCP proxy that sits between an AI client (Claude, Cursor, etc.) and the remote Squidler MCP server. It forwards all tools, resources, and prompts transparently, while adding local Chrome session management for testing localhost URLs.
How it works
AI Client (stdio) ←→ MCP Proxy ←→ Remote Squidler MCP (HTTP)
↕
Local Chrome ←→ CDP Proxy (WebSocket)The proxy intercepts test_case_run and test_case_run_standalone calls — when local Chrome mode is enabled, it automatically creates a CDP session and routes the test through your local browser instead of the cloud worker's Chrome. Same handling applies to test_cases_run_all and test_cases_run_by_label.
Related MCP server: chrome-faithful
Quick Start
Run directly with npx — no install or API key needed:
npx @squidlerio/squidler-mcpOn first use, a browser window opens for you to sign in to Squidler. Your session is saved locally so you only need to do this once.
Claude Code
claude mcp add squidler -- npx -y @squidlerio/squidler-mcpCursor / Other MCP Clients
Add to your MCP client configuration:
{
"mcpServers": {
"squidler": {
"command": "npx",
"args": ["-y", "@squidlerio/squidler-mcp"]
}
}
}CLI Commands
# Sign in to Squidler (happens automatically on first use)
squidler-mcp login
# Sign out and clear saved session
squidler-mcp logout
# Download Chrome headless shell for local testing
squidler-mcp download-chromeLocal Session Tools
These tools are added by the proxy (not available on the remote server):
local_session_start— Enable local Chrome mode. Acceptsheadless(boolean, default: true). Chrome is launched on the first test-running tool call.local_session_stop— Disable local Chrome mode and stop any active session.local_session_status— Check if local Chrome mode is enabled and if a session is active.
When local Chrome mode is enabled, the test-running tools — test_case_run, test_case_run_standalone, test_cases_run_all, test_cases_run_by_label — automatically create/recycle a CDP session and route through your local Chrome. Back-to-back tests get a fresh Chrome instance each time.
Advanced: API Key Override
If you prefer to use an API key instead of OAuth login, set the SQUIDLER_API_KEY environment variable:
{
"mcpServers": {
"squidler": {
"command": "npx",
"args": ["-y", "@squidlerio/squidler-mcp"],
"env": {
"SQUIDLER_API_KEY": "your-api-key"
}
}
}
}Variable | Required | Default | Description |
| No | — | API key override (skips OAuth login) |
| No |
| Remote MCP server URL |
Development
bun install
bun run start # Run CLI
bun run mcp-proxy # Run MCP proxy
bun run build # Build for npm publishingThis server cannot be deployed
Maintenance
Related MCP Connectors
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
A paid remote MCP for AI agent browser MCP session, built to return verdicts, receipts, usage logs,
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI agents faithful control of real, logged-in Chrome profiles via a secure local bridge and extension, with exact multi-profile routing and no debug profiles or remote debugging ports.5MIT
- AlicenseNot gradedqualityBmaintenanceShares one Chrome browser across multiple AI coding sessions via an MCP proxy, adding lifecycle management, tool filtering, and anti-detection while wrapping the upstream chrome-devtools-mcp server.6 npm2MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC