Germany Tenders
Germany public procurement MCP — official German government tenders (keyless).
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http germany-tenders 'https://gateway.pipeworx.io/germany-tenders/mcp'{
"mcpServers": {
"germany-tenders": {
"type": "http",
"url": "https://gateway.pipeworx.io/germany-tenders/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-germany-tenders
Germany public procurement MCP — official German government tenders (keyless).
Part of Pipeworx — an MCP gateway connecting AI agents to 1686+ live data sources.
Tools
| Tool | Description |
|---|---|
germany_search_tenders | Search official GERMAN government public-procurement tenders (Öffentliche Vergabe / Ausschreibungen) from the federal Bekanntmachungsservice open-data feed (oeffentlichevergabe.de), Open Contracting Data Standard (OCDS, CC0). Returns each notice shaped: ocid, title, buyer/Vergabestelle, contract value in EUR, procurement category, CPV code, procurement method, submission deadline, and publish date. Filter by publish-date range and/or a keyword (matched against title, description, buyer, and CPV description — German text). Defaults to the most recent days if no dates given. Can answer wide date ranges (months) as well as very recent days. Data covers Germany only. |
germany_buyer_spend_history | Procurement spend history for a GERMAN government buyer (Vergabestelle) — e.g. a city, a ministry, a university hospital — across German OCDS tender notices (oeffentlichevergabe.de, CC0). Matches the buyer name (case-insensitive substring, e.g. "Universitätsklinikum Halle", "Stadt Angermünde"). Returns process count, how many of those disclosed a EUR value (German notices below the EU publication threshold frequently omit contract value — this is reported, not hidden), total disclosed spend in EUR, top procurement categories, and a sample of recent processes. Spans up to 12+ months (see data_as_of in the response for the current coverage). |
germany_supplier_win_history | Contract-win history for a GERMAN supplier/contractor (e.g. "Uniola AG", "System Strobel GmbH") across German OCDS tender notices (oeffentlichevergabe.de, CC0) — which buyers they won work from, award dates, and disclosed EUR values where published. COVERAGE IS GENUINELY PARTIAL: the winning supplier and award value are disclosed on only a small minority of German notices (below-threshold contracts routinely omit both) — the response reports won_count vs. value_disclosed_count so that gap is visible rather than read as "no data". See data_as_of in the response for the current coverage. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"germany-tenders": {
"url": "https://gateway.pipeworx.io/germany-tenders/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/germany-tenders/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 1686+ 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/germany_search_tenders \
-H 'Content-Type: application/json' \
-d '{"date_from":"2024-11-01","date_to":"2024-11-15","query":"Bauarbeiten","limit":25}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/germany_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": {
"germany-tenders": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-germany-tenders"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-germany-tendersIt 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 Germany Tenders data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Questions fréquentes
Qu'est-ce que Germany Tenders ?
Germany public procurement MCP — official German government tenders (keyless).
Comment installer Germany Tenders ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http germany-tenders 'https://gateway.pipeworx.io/germany-tenders/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Germany Tenders ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Germany Tenders est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Germany Tenders ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.