flashid-mcp

中文文档

MCP (Model Context Protocol) server for the FlashID client. It lets AI agents — Claude Code, Claude Desktop, Cursor and any other MCP client — manage your FlashID browser profiles, proxies and folders, and open/close browsers with automation endpoints, all through natural language.

Requirements

• The FlashID desktop app installed and running, with Local API enabled (FlashID → Settings → Local API)

• Your FlashID API key (FlashID → Settings → API Access)

• Node.js ≥ 18 (npx comes with it)

Related MCP server: hotlogin-mcp

Setup

Claude Code

claude mcp add flashid -e FLASHID_API_KEY=your-api-key -- npx -y flashid-mcp

Claude Desktop / Cursor

{
  "mcpServers": {
    "flashid": {
      "command": "npx",
      "args": ["-y", "flashid-mcp"],
      "env": { "FLASHID_API_KEY": "your-api-key" }
    }
  }
}

Environment variables

CLI flags --api-key / --port override the environment.

Tools

Try it

Create 3 Windows 11 profiles named shop-1..3, bind my proxy 1.2.3.4:1080 to them, and open the first one.

create_profile only requires system — omitted fingerprint fields are auto-generated as a coherent random fingerprint by FlashID.

Page automation

open_browser returns CDP automation endpoints:

{ "id": "…", "ws": { "puppeteer": "ws://127.0.0.1:9222/devtools/browser/…", "selenium": "127.0.0.1:9222" }, "debug_port": 9222 }

Hand ws.puppeteer to Playwright/Puppeteer (puppeteer.connect({ browserWSEndpoint })) or to a browser-automation MCP server to drive pages inside the fingerprinted browser.

Troubleshooting

Run the check_connection tool first — it tells you whether the FlashID app is reachable and whether the API key is configured. Full API reference: docs.flashid.app.

Development

npm install
npm run build        # tsc → dist/
npm test             # vitest
npm run check-coverage  # tool coverage vs contract/openapi.json

License

MIT