Swiss Procurement MCP server

<!-- mcp-name: io.github.malkreide/swiss-procurement-mcp -->

Part of the Swiss Public Data MCP Portfolio — open-source MCP servers connecting AI agents to Swiss public and open data.

This is a private project. It is independent of any employer or institutional affiliation and represents no official position of any authority.

swiss-procurement-mcp

MCP server for Swiss public procurement — read access to the official simap.ch API, covering all cantons and the Confederation, updated intraday.

🎯 Anchor demo query

«Which school-building tenders did the City of Zurich publish in 2026, which BKP construction categories do they concern, and who are the procuring offices?»

A single searchprocurementsdetailed(query="Schulhaus", canton="ZH", publishedfrom="2026-01-01") returns the leading tenders already expanded with their BKP construction codes and procuring offices — connecting procurement to school-building planning in one call (optionally paired with searchconstruction_codes to resolve a category).

Demo

Why this server exists

Swiss public procurement is published on simap.ch. The platform's web UI is searchable by hand, but the amtsblatt-mcp server only reaches the three cantons (AR, BS, TI) that still mirror tenders to the Amtsblattportal — Zurich among the missing.

simap closes that gap: it operates a documented OpenAPI 3 read API (v1.5.1) whose search and detail endpoints are marked security: None and are callable without authentication. This server wraps exactly those read endpoints.

Mnemonic: The web UI is the front door; the API is the loading dock. Probe the dock.

Architecture decision

Architecture A (live API only, short-lived cache).

confirmed working live (2026-07-26).

• The public search, detail and reference endpoints are unauthenticated and were

submitting offers) are out of scope — this server never writes.

• Publications change intraday, so the cache TTL is deliberately short (30 min).
• The ~200 write / my/ / OIDC-protected endpoints (publishing tenders,

Every response carries source and provenance (live_api / cached / degraded). Upstream failure yields a degraded envelope, never a silent empty list.

Live-probe findings (2026-07-26)

Known findings

Shortened. The full README is on GitHub.