FireKey MCP
Manage FireKey browser profiles and browser lifecycles through an authenticated localhost API.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
firekey-mcpclaude mcp add firekey-mcp -e 'FIREKEY_API_KEY=<your firekey_api_key>' -e 'FIREKEY_PORT=<FIREKEY_PORT>' -- npx -y firekey-mcp@0.1.3
{
"mcpServers": {
"firekey-mcp": {
"command": "npx",
"args": [
"-y",
"firekey-mcp@0.1.3"
],
"env": {
"FIREKEY_API_KEY": "<your firekey_api_key>",
"FIREKEY_PORT": "<FIREKEY_PORT>"
}
}
}
}
Environment variables
FIREKEY_API_KEYrequired secret API key from the FireKey desktop app under Settings > Local API & MCP.FIREKEY_PORTOptional localhost port override; otherwise auto-discovered from FireKey.
Frequently asked questions
What is FireKey MCP?
Manage FireKey browser profiles and browser lifecycles through an authenticated localhost API.
How do I install FireKey MCP?
It runs on your machine. In Claude Code: claude mcp add firekey-mcp -e 'FIREKEY_API_KEY=<your firekey_api_key>' -e 'FIREKEY_PORT=<FIREKEY_PORT>' -- npx -y firekey-mcp@0.1.3. For other clients, paste the JSON configuration from this page into their MCP settings.
Does FireKey MCP need an API key?
Yes. It expects FIREKEY_API_KEY, which you set in its configuration.
Who maintains FireKey MCP?
It is published by partnerhbhl. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.