FireKey MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 9 installs a week from npm.
Manage FireKey browser profiles and browser lifecycles through an authenticated localhost API.
Today is the operative word: we check FireKey MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 firekey-mcp -- npx -y firekey-mcp
{
"mcpServers": {
"firekey-mcp": {
"args": [
"-y",
"firekey-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.firekey-mcp]
command = "npx"
args = ["-y", "firekey-mcp"]
{
"mcpServers": {
"firekey-mcp": {
"args": [
"-y",
"firekey-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"firekey-mcp": {
"args": [
"-y",
"firekey-mcp"
],
"command": "npx"
}
}
}
Your AI agent drives a real, logged-in Chrome — test authenticated apps, 2FA flows, scrape logins
Local Playwright browser through residential proxies — agent picks country + sticky identity
MCP server for loading authenticated web pages using Chrome DevTools Protocol
Browser automation MCP server: navigate, fill forms, click, screenshot, and manage tabs
Drive Argus anti-detect browser profiles: isolated identities with their own fingerprint and proxy.
Local browser automation for MCP clients powered by DrissionPage.
Local MCP for Power Automate with browser-backed auth, target locking, review diff, and rollback.
One audio queue across Spotify, the browser, local files and whatever is already playing.
Answers built from our own checks of this server.