Boamp MCP Server

Boamp MCP server exists for a simple reason — assistants are far more useful when they can act on Boamp directly instead of describing what you should do. Serveur MCP (Model Context Protocol) pour interroger l'API BOAMP et récupérer les avis de marchés publics. Ce serveur permet de rechercher des marchés publics en utilisant divers critères et d'obtenir des détails complets sur des marchés.

Setting it up

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

What the assistant can call

Once Boamp is connected, these are the calls the assistant has available:

• type — Type de marché (SERVICES, TRAVAUX, FOURNITURES)
• limit — Nombre maximum de résultats à retourner
• sort_by — Champ de tri (dateparution, datelimitereponse)
• departments — Liste des départements (codes)
• Outils — The Outils tool exposed by this server
• get_public_markets — The get_public_markets tool exposed by this server
• get_market_details — The get_market_details tool exposed by this server
• Exemples — The Exemples tool exposed by this server
• Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Before you rely on it

• 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 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Boamp.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the boamp mcp server does with a few real requests.

Choosing this one

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. Boamp's toolset — type, limit, sort_by and 6 more — is a fair guide to whether it matches your workflow. It is maintained by stefw; 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.