Fingerprint MCP Server

If you already use Fingerprint, the fingerprint mcp server is the piece that lets your assistant work with it directly. Device intelligence for AI agents: Fingerprint events, smart signals, and API key management.

What the server does

• Run locally or use managed instance at https://mcp.fpjs.io/mcp
• Event tools — Retrieve and search identification events with full smart signal data
• Management tools — Manage workspace environments and API keys
• Onboarding prompt — Guided setup for integrating Fingerprint into a project
• Supports both stdio and streamable-http transports
• Optional HTTPS with TLS certificates

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• get_current_time — Return the current date/time in UTC (and an optional IANA timezone)
• get_event — Retrieve a specific identification event by ID
• search_events — Search events with filters (visitor, IP, smart signals, time range)
• list_environments — List workspace environments with pagination
• get_api_key — Get details of a specific API key
• list_api_keys — List API keys with optional type/status/environment filters
• create_environment — Create a new workspace environment
• update_environment — Update an existing workspace environment
• delete_environment — Delete a workspace environment
• create_api_key — Create a new API key (public/secret/proxy)
• update_api_key — Update an existing API key
• delete_api_key — Delete an API key (irreversible)

Credentials and setup notes

Configuration is passed through the environment: FINGERPRINT_SERVER_API_KEY, FINGERPRINT_SERVER_API_URL, FINGERPRINT_MANAGEMENT_API_KEY, FINGERPRINT_MANAGEMENT_API_URL, FINGERPRINT_REGION, MCP_TLS_KEY, MCP_AUTH_TOKEN, FINGERPRINT_PUBLIC_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fingerprint's toolset — get_current_time, get_event, search_events and 9 more — is a fair guide to whether it matches your workflow. It is maintained by fingerprintjs; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Fingerprint.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.