MCP Servers
qune-tech/ocds-mcp
MCP server for German public procurement data — semantic search and tender matching for Claude, GPT, Cursor, and LM Studio
Our verdict
We have not reviewed qune-tech/ocds-mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About qune-tech/ocds-mcp
A Rust-based MCP server that enables semantic search and tender matching across German public procurement data. It provides an API for large language models like Claude, GPT, Cursor, and LM Studio to query and match procurement notices.
Best for
Developers building AI assistants that need to search or match German public tenders
Use cases
- Searching for relevant public tenders by natural language description
- Matching procurement notices to supplier capabilities or project needs
- Integrating procurement discovery into an AI-assisted workflow
Notes
3 stars on GitHub. Last updated 2026-03-24. Licensed MIT.
Pros
- Provides a specialized interface for German procurement data
- Written in Rust for performance and reliability
- Works across multiple popular LLM platforms
Cons
- Limited to German public procurement data only
- Small project with only 3 stars, indicating a nascent community
- Requires setup and integration with an MCP-compatible client
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
npx @qune-tech/vergabe-mcp --api-key sk_live_YOUR_KEY_HERETools exposed
search_textlist_releasesget_releaselinked_noticesget_index_infocreate_company_profileupdate_company_profileget_company_profilelist_company_profilesdelete_company_profilematch_tenders
Clients the listing names (not checked here)
Claude Desktop, Claude Code, Cursor
Install
Add qune-tech/ocds-mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --env OCDS_API_KEY=YOUR_OCDS_API_KEY --transport stdio qune-tech-ocds-mcp -- npx -y @qune-tech/ocds-mcp@0.4.0Needs OCDS_API_KEY: replace each YOUR_ value with your own.
Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"qune-tech-ocds-mcp": {
"command": "npx",
"args": [
"-y",
"@qune-tech/ocds-mcp@0.4.0"
],
"env": {
"OCDS_API_KEY": "YOUR_OCDS_API_KEY"
}
}
}
}Needs OCDS_API_KEY: replace each YOUR_ value with your own.
Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"qune-tech-ocds-mcp": {
"command": "npx",
"args": [
"-y",
"@qune-tech/ocds-mcp@0.4.0"
],
"env": {
"OCDS_API_KEY": "YOUR_OCDS_API_KEY"
}
}
}
}Needs OCDS_API_KEY: replace each YOUR_ value with your own.
VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"inputs": [
{
"type": "promptString",
"id": "ocds-api-key",
"description": "API key (sk_live_...) from https://vergabe-dashboard.qune.de/app/api-keys",
"password": true
}
],
"servers": {
"qune-tech-ocds-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@qune-tech/ocds-mcp@0.4.0"
],
"env": {
"OCDS_API_KEY": "${input:ocds-api-key}"
}
}
}
}Needs OCDS_API_KEY: replace each YOUR_ value with your own.
Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.qune-tech-ocds-mcp]
command = "npx"
args = ["-y", "@qune-tech/ocds-mcp@0.4.0"]
env_vars = ["OCDS_API_KEY"]Needs OCDS_API_KEY: replace each YOUR_ value with your own.
- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What qune-tech/ocds-mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.4.0Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 0.4.0Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 0.4.0Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.4.0Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 0.4.0Config checked | Codex docs |
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.