FireKey MCP

io.github.partnerhbhlPublished by GitHub account partnerhbhlv0.1.3Updated Oct 25, 2026

Manage FireKey browser profiles and browser lifecycles through an authenticated localhost API.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

FireKey MCP lets an assistant manage FireKey browser profiles and browser lifecycles through an authenticated localhost API on the user's desktop.

What you can do
Manage FireKey browser profiles through the local API, including creating and handling profiles for different browsing contexts. Control browser lifecycles, starting and managing browser instances tied to those profiles. All actions go through an authenticated localhost API exposed by the FireKey desktop app. The manifest lists no individual tools, so exact operations depend on the running FireKey app.
When to use it
Useful when you already run the FireKey desktop app and want an assistant to set up or manage browser profiles and start or stop browsers without manual clicking. It is desktop-only, so it does not suit headless or server environments.
Requirements
A local process started via the npm package firekey-mcp over stdio. Requires the FireKey desktop app running on the same machine, with its Local API and MCP feature enabled. Requires an API key supplied in the FIREKEY_API_KEY environment variable, taken from the FireKey app under Settings > Local API & MCP. An optional FIREKEY_PORT variable overrides the localhost port; otherwise the port is auto-discovered from FireKey.
Before you install
The FIREKEY_API_KEY secret grants access to the local FireKey API, so keep it out of shared logs and repositories. The server can create and manage browser profiles and start or stop browsers, which changes local state. It is desktop-only and relies on the FireKey app being installed and running.

Installation

In SourceWeft

  1. Open FireKey MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.