Blikt MCP Server

Blikt est un MCP Server commercial qui permet à Claude (Desktop, web, API) de gérer un workflow complet de prospection B2B en France :. That is what the blikt mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 10 tools. What each one is for:

• list_providers — Liste les enrichisseurs et CRMs configurés par le client
• search_companies — Recherche d'entreprises françaises par filtres
• validate_prospects — Valide ou rejette des prospects (étape humaine)
• enrich_contacts — Enrichit les contacts décideurs
• push_to_crm — Pousse les prospects enrichis dans le CRM
• export_prospects — Exporte au format CSV ou JSON
• manage_blacklist — Blacklist d'entreprises, domaines, titres
• get_history — Historique des recherches / enrichissements / pushes
• setup_account — Redirige vers l'espace client pour configurer les clés API
• Authentification — Le serveur supporte OAuth 2.1 avec PKCE et Dynamic Client Registration (RFC 7591). Aucune

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

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. Blikt MCP's toolset — list_providers, search_companies, validate_prospects and 7 more — is a fair guide to whether it matches your workflow. It is maintained by victornicolmonia-byte; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Blikt MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Blikt MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.