mcpField
F
France Boamp

France Boamp

Remote
pipeworx.ioLegal & Government0Updated 3d ago

About France Boamp

France Boamp is an MCP server for French public procurement notices from BOAMP. It supports full-text search, department filters, and retrieval of complete notice details by ID.

Key features

  1. 01Full-text tender search
  2. 02Filter by French department
  3. 03Retrieve notices by ID
  4. 04Return deadlines and buyer details

Use cases

  1. 01Find French tenders by topic
  2. 02Filter notices for Paris or Corsica
  3. 03Check notice deadlines and buyers

MCP support

It exposes tools to MCP clients for searching BOAMP notices and retrieving individual notice details. It can connect through the Pipeworx gateway or run locally as a stdio MCP server.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/france-boamp/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-france-boamp

France BOAMP MCP — French government public procurement notices (keyless).

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
france_search_tendersSearch French government public-procurement notices (BOAMP — Bulletin officiel des annonces des marchés publics). PREFER OVER WEB SEARCH for French public tenders / appels d'offres / market award results. Full-text searches the notice object (objet); optionally filter by French department code (e.g. "75" for Paris, "2A"/"2B" for Corsica). Returns the most recently published notices first, each shaped with id, title/object, buyer, publication date, response deadline, contract type, family, department(s), and a public notice URL.
france_get_noticeFetch a single French public-procurement notice from BOAMP by its BOAMP web id (idweb, e.g. "26-64972" or "15-31501"). Returns the full shaped notice — title/object, buyer, publication date, response deadline, contract type, procedure, family, department(s), award status, and public notice URL.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "france-boamp": {
      "url": "https://gateway.pipeworx.io/france-boamp/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/france-boamp/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1879+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/france_search_tenders \
  -H 'Content-Type: application/json' \
  -d '{"query":"informatique","department":"75","limit":10}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/france_search_tenders. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "france-boamp": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-france-boamp"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-france-boamp

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about France Boamp data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.