vergabe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | The port to listen on when using Streamable HTTP mode (e.g., 3000) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tendersA | Searches lots on oeffentlichevergabe.de. Defaults to open lots of the competition notice types (cn-standard, cn-social, cn-desg, subco, qu-sy, pin-cfc-standard, pin-cfc-social), newest first. Use search_tenders_raw for anything this does not cover. |
| get_tenderA | Fetches a single notice. 'summary' extracts the fields a bidder decides on (deadlines, lot values, suitableFor, document links); the other formats are returned verbatim. |
| search_tenders_rawA | Posts a WHERE/FROM/PAGE/ORDER query to /bkmk/searches unchanged. Operators: =, >, >=, <, <=, IN, STARTS_WITH, CONTAINS, MATCH_ALL, MATCH_ANY, RANGE_DAYS. Fields on lots: allFreeText, description, allCpvCodes, allContractNatures, active, noticeType, suitableFor (freelance|selbst|startup|other-sme), estimatedValue ('150000 EUR'), publicationDate, firstDeadline, allDeadlines, allPlacesOfPerformanceNutsCodes, contractingPlatform, procedureType, procedureLegalBasis, procedureIdentifier. Text and temporal operators take exactly one operand; IN and STARTS_WITH OR a list. RANGE_DAYS n means field >= midnight Europe/Berlin of today + n days, not a window. See the vergabe://api-reference resource for the full contract. |
| lookup_codeB | Resolves a CPV or NUTS code to its official description. |
| get_export_urlA | Builds the URL of the official bulk export for one day or month. The file is a large ZIP, so download it outside this server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find-solo-tenders | Searches for small, freelance-suitable lots and triages the results. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api-reference | Endpoints, search grammar, field table and quirks of the oeffentlichevergabe.de backend. |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: searching tenders, fetching details, raw querying, code lookup, and export URL generation. There is no overlap between their purposes.
All tool names follow a clear verb_noun pattern (search_tenders, get_tender, search_tenders_raw, lookup_code, get_export_url). The conventions are uniform and predictable.
Five tools are well-scoped for a public procurement domain. Each tool addresses a necessary function without being excessive or insufficient.
Core workflows for searching, fetching, raw querying, code lookup, and export are covered. Minor gaps like bulk export download instructions are handled via external guidance, which is acceptable.