MCP server for German public procurement data — semantic search and tender matching for Claude, GPT, Cursor, and LM Studio
MCP server for German public procurement data — semantic search and tender matching for Claude, GPT, Cursor, and LM Studio. Exposed over MCP by the german public procurement data (ocds) — semantic search, tender matching, company profiles mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Local MCP server for German public procurement search. Connects your AI assistant (Claude, GPT, etc.) to the Vergabe Dashboard API for semantic search, tender matching, and company-profile management.
Everything the assistant can do here goes through one of these:
search_text — Semantic search across all tenders (query embedded locally)list_releases — Filter and browse tenders by phase, CPV prefix, country, value range, deadline, buyer, procurement methodget_release — Raw eForms XML envelope for one OCID (optional notice_id selects a sibling)linked_notices — A procurement's notice lineage (PIN→CN→CAN) as {ocid, notice_id} refsget_index_info — API health/version, embedder status, and embedding-contract checkcreate_company_profile — Create a matching profile for your company (stored locally)update_company_profile — Update an existing profileget_company_profile — View profile detailslist_company_profiles — List all your profilesdelete_company_profile — Delete a profilematch_tenders — Match a profile against all tenders by semantic similarity (vector embedded locally)You will need one environment variable: VERGABE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. German Public Procurement Data (OCDS) — Semantic Search, Tender Matching, Company Profiles's toolset — search_text, list_releases, get_release and 8 more — is a fair guide to whether it matches your workflow. It is maintained by qune-tech; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_text | Semantic search across all tenders (query embedded locally) |
| list_releases | Filter and browse tenders by phase, CPV prefix, country, value range, deadline, buyer, procurement method |
| get_release | Raw [eForms](https://vergabe-dashboard.qune.de/wissen/eforms/) XML envelope for one OCID (optional notice_id selects a sibling) |
| linked_notices | A procurement's notice lineage (PIN→CN→CAN) as {ocid, notice_id} refs |
| get_index_info | API health/version, embedder status, and embedding-contract check |
| create_company_profile | Create a matching profile for your company (stored locally) |
| update_company_profile | Update an existing profile |
| get_company_profile | View profile details |
| list_company_profiles | List all your profiles |
| delete_company_profile | Delete a profile |
| match_tenders | Match a profile against all tenders by semantic similarity (vector embedded locally) |
Using the binary directly:
```json
{
"mcpServers": {
"vergabe": {
"command": "vergabe-mcp",
"args": ["--api-key", "sk_live_YOUR_KEY_HERE"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| VERGABE_API_KEY | Credential the server authenticates with. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.