Skip to main content
Glama
partnerhbhl

FireKey MCP Server

by partnerhbhl

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FIREKEY_PORTNoFireKey Local API port (optional, auto-detected if not set)
FIREKEY_API_KEYYesAPI key for authentication

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
browser_startC

Start a browser profile. Returns WebSocket endpoints for Puppeteer/Selenium automation.

browser_stopB

Stop a running browser profile.

browser_activeA

List currently running browser profiles with their WebSocket endpoints.

profile_listA

List browser profiles with pagination and filtering.

profile_createC

Create a new browser profile with fingerprint and proxy settings.

profile_updateC

Update an existing browser profile.

profile_deleteA

Delete browser profiles (soft delete to trash).

profile_moveB

Move profiles to a different group.

profile_delete_cacheA

Delete cached data for browser profiles (cookies, history, localStorage, etc.).

profile_cookiesA

Get cookies from a browser profile (from running browser via CDP, or from local files).

group_listA

List profile groups with optional name search.

group_createB

Create a new profile group.

group_updateC

Update an existing group.

proxy_listB

List saved proxy configurations.

proxy_createC

Create a new proxy configuration.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 15 tools

Disambiguation5/5

Each tool targets a distinct resource-action pair: groups, proxies, browser execution, and profile management are clearly separated. Even closely related tools like profile_delete and profile_delete_cache are unambiguous from their names.

Naming Consistency4/5

Tool names consistently use a resource_action pattern in snake_case (group_create, proxy_list, browser_start, profile_update). Minor deviations like profile_cookies and browser_active are not actions, but they are still predictable and readable.

Tool Count5/5

15 tools is within the well-scoped range and each tool addresses a concrete need for browser profile management, proxy management, group organization, and runtime browser control. There are no redundant or trivial tools.

Completeness3/5

Profile and browser management are well covered, but auxiliary resources have notable lifecycle gaps: proxies cannot be updated or deleted, and groups cannot be deleted. This leaves no way to remove stale proxy configurations or groups, which agents may need to do.

Maintenance

ActivityMaintained
ResponsivenessNo issues