browse_bkp_tree
Browse the BKP code hierarchy (Swiss construction cost plan)
LABSCO SUMMARY
The classification codes a tender search depends on are findable in the same session as the search.
Filtering simap.ch usefully means holding CPV, BKP, NPK or OAG codes, and each of the four is both keyword-searchable and browsable as a hierarchy here, so a query does not stall on a number nobody remembers. The publication history is what completes a tender's story, since corrections and awards are separate publications against the same project. Language is a parameter on nearly every call, which matters in a country that publishes procurement in several.
What it is
A client for simap.ch covering tender search and detail, the Swiss procurement classification trees, and the bodies that publish.
What you get
- Tender search filtered by publication date range, cantons, CPV and BKP codes, process types, project subtypes, publication types and issuing organisation.
- Full detail for one tender, with the raw record available when the summary is not enough.
- Four classification systems searchable by keyword or number and browsable as trees: CPV, the BKP construction cost plan, the NPK standardised positions catalogue and the OAG object type classification.
- The Swiss cantons with their codes, the public institutions that publish tenders, and procurement offices searched by name or institution.
- A project's publication history, including corrections and awards.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y @digilac/simap-mcp
USE CASES
01
Finding tenders in your field and your canton
Canton codes and CPV codes are the two filters that matter most, and both are resolvable before the search runs.
02
Working out which classification code actually covers your work
Keyword search finds a candidate; browsing the tree around it shows whether the parent or a sibling is the better filter.
03
Following what happened to a tender after it was published
Corrections and awards are separate publications on the same project, so the detail alone leaves the ending out.
04
Identifying who is actually doing the buying
Institution and procurement office are different levels, and knowing which one publishes is what makes a follow-up call possible.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
browse_cpv_tree
Browse the CPV code hierarchy (shows subcategories of a parent code)
browse_npk_tree
Browse the NPK code hierarchy (standardized positions catalog)
browse_oag_tree
Browse the OAG code hierarchy (object type classification)
get_publication_history
Get the publication history for a project (corrections, awards, etc.)
get_tender_details
Get detailed information about a specific tender
list_cantons
List all Swiss cantons with their codes (useful for search filters)
list_institutions
List Swiss public institutions (Confederation, cantons, municipalities) that publish tenders
search_bkp_codes
Search BKP (Swiss construction cost plan) codes by keyword or number
search_cpv_codes
Search CPV (Common Procurement Vocabulary) codes by keyword or partial code number
search_npk_codes
Search NPK (standardized positions catalog) codes by keyword or number
search_oag_codes
Search OAG (object type classification) codes by keyword or number
search_proc_offices
Search public procurement offices by name or institution
search_tenders
Search public tenders on simap.ch with filters by date, canton, CPV codes, and other criteria
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected.
Requires
- npx on PATH
- Node.js ≥ 22
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"simap-mcp": {
"command": "npx",
"args": [
"-y",
"@digilac/simap-mcp"
]
}
}
}npx
TERMINAL
npx -y @digilac/simap-mcp
