OCDS German Procurement Search

Name: OCDS German Procurement Search
Author: qune-tech

by qune-techversion 0.4.0i★ –iRuns on your computer

Registry nameio.github.qune-tech/ocds-mcp

Install

Overview

Description from the maker (original English)

Search and match German public procurement tenders (OCDS) from your local LLM.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: OCDS_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: OCDS_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ocds": {
      "command": "npx",
      "args": [
        "-y",
        "@qune-tech/ocds-mcp"
      ],
      "env": {
        "OCDS_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ocds --env OCDS_API_KEY=your-value -- npx -y @qune-tech/ocds-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ocds": {
      "command": "npx",
      "args": [
        "-y",
        "@qune-tech/ocds-mcp"
      ],
      "env": {
        "OCDS_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ocds": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@qune-tech/ocds-mcp"
      ],
      "env": {
        "OCDS_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

OCDS_API_KEY secret required env
API key (sk_live_...) from https://vergabe-dashboard.qune.de/app/api-keys

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account qune-tech, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7271 servers in this category
Published to the registry more recently than 6% of the other 7271 servers in this category
Basic checks equal to or better than 100% of the other 7271 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is OCDS German Procurement Search safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: OCDS_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

vergabe-mcp

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.

Your queries and company profiles never leave your machine. They are embedded locally with a multilingual ONNX model; only the resulting embedding vectors, OCIDs, and filter values are sent to the API. Data minimisation by design.

Hosted alternative: if you just want search from your AI assistant, there is a hosted MCP connector (OAuth sign-in, no installation) — see the setup guide. This local server is for running the client in your own environment: queries and profiles are embedded locally, only vectors and filter values leave the machine, and it unlocks API-key features.

New to German public procurement? The Vergabe Dashboard knowledge base explains eForms, EU thresholds, and the tender lifecycle, and KI für Vergabe covers the hosted AI side of this server.

Quick Start

1. Get an API key

Sign up at vergabe-dashboard.qune.de and create an API key. API keys require an active Pro plan (€99/month; the local server itself is free and open source — the API gate rides key issuance).

2. Install

Via npx (easiest — downloads the correct binary automatically):

npx @qune-tech/vergabe-mcp --api-key sk_live_YOUR_KEY_HERE

Or download a pre-built binary from GitHub Releases:

Platform	Download
Linux x86_64	vergabe-mcp-linux-x86_64.tar.gz
macOS Apple Silicon	vergabe-mcp-macos-arm64.tar.gz
Windows x86_64	vergabe-mcp-windows-x86_64.zip

Linux / macOS:

# Example for Linux x86_64 — adjust the filename for your platform

tar xzf vergabe-mcp-linux-x86_64.tar.gz sudo mv vergabe-mcp /usr/local/bin/vergabe-mcp

Windows: Extract the zip and move vergabe-mcp.exe somewhere on your PATH.

Or build from source:

git clone https://github.com/qune-tech/vergabe-mcp.git

cd vergabe-mcp cargo build --release

Binary at target/release/vergabe-mcp

3. Configure your AI client

Claude Desktop — edit claude_desktop_config.json:

Using npx:

"mcpServers": { "vergabe": { "command": "npx", "args": ["-y", "@qune-tech/vergabe-mcp", "--api-key", "sk_live_YOUR_KEY_HERE"] } } }

Using the binary directly:

"mcpServers": { "vergabe": { "command": "vergabe-mcp", "args": ["--api-key", "sk_live_YOUR_KEY_HERE"] } } }

Claude Code — add .mcp.json to your project root:

Using npx:

"mcpServers": { "vergabe": { "command": "npx", "args": ["-y", "@qune-tech/vergabe-mcp", "--api-key", "sk_live_YOUR_KEY_HERE"] } } }

Using the binary directly:

"mcpServers": { "vergabe": { "command": "vergabe-mcp", "args": ["--api-key", "sk_live_YOUR_KEY_HERE"] } } }

Cursor — Settings → MCP Servers → Add:

Using npx:

Command: npx
Args: -y @qune-tech/vergabe-mcp --api-key sk_live_YOUR_KEY_HERE

Using the binary directly:

Command: vergabe-mcp
Args: --api-key sk_live_YOUR_KEY_HERE

LM Studio — Settings → MCP → Add Server:

Click + Add Server and choose STDIO
Fill in:

Using npx:

Name: vergabe
Command: npx
Arguments: -y @qune-tech/vergabe-mcp --api-key sk_live_YOUR_KEY_HERE

Using the binary directly:

Name: vergabe
Command: full path to the binary, e.g. /usr/local/bin/vergabe-mcp
Arguments: --api-key sk_live_YOUR_KEY_HERE

Click Save
In the chat, select a model that supports tool use and enable the vergabe server

LM Studio requires models with tool-calling support (e.g. Qwen 2.5, Mistral, Llama 3.1+).

Smaller models may not use all 11 tools reliably — 7B+ recommended.

Replace sk_live_YOUR_KEY_HERE with your actual API key. You can also pass the key via the VERGABE_API_KEY environment variable.

Available Tools (11)

Tool	Description
`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 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)

CLI Options

Usage: vergabe-mcp [OPTIONS]

Options: --db Local profiles database [default: profiles.db] --data-dir Data directory [default: data] --api-url Vergabe Dashboard API [default: https://vergabe-dashboard.qune.de] --api-key API key [env: VERGABE_API_KEY] -h, --help Print help

How It Works

LLM ←stdio→ vergabe-mcp (local)

│ Local: company profiles (SQLite) + sentence embedder (ONNX) │ HTTPS: vectors, OCIDs, filter values, API key └──HTTPS──→ Vergabe Dashboard API (/api/v1)

The MCP server runs locally on your machine:

Company profiles (name, description, CPV interests, location) are stored in a local SQLite database — they never leave your network.
Text embeddings are computed locally with a multilingual ONNX model (multilingual-e5-small, 384-dim). Search queries use the query: prefix and go to POST /api/v1/search/vector; profile descriptions use the passage: prefix and go to POST /api/v1/match/vector.
Only embedding vectors (384 floats), the OCIDs you fetch, filter values, and your API key are sent to the API. Your query and profile text stay local.

Privacy & data flow

What stays on your machine: profile text, search-query text, CPV interests, location.

What the API sees: embedding vectors, the OCIDs you read, the filter values you use, and your API key. These reveal *commercial interest* (which sectors, buyers, value bands, tenders you look at) but not the underlying text. Embedding vectors are a derived, pseudonymous representation — minimisation, not elimination.

First-run model download: on first use the server downloads the embedding model from huggingface.co:

What: model.onnx + tokenizer.json, ~118 MB total.
When: the first time the embedder runs; cached afterwards at ~/.cache/vergabe/models/multilingual-e5-small.
From: huggingface.co (a US-operated third party). No user data is sent in this fetch — it is a plain model download.

For air-gapped / enterprise installs, place model.onnx and tokenizer.json in the cache directory above and the runtime download is skipped.

Requirements

An API key from vergabe-dashboard.qune.de on the Pro plan (€99/month)
~120 MB disk space for the ONNX model (downloaded automatically on first run)
Internet connection to reach the API

License

MIT — see LICENSE.

OCDS German Procurement Search

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

vergabe-mcp

Quick Start

1. Get an API key

2. Install

Binary at target/release/vergabe-mcp

3. Configure your AI client

Available Tools (11)

CLI Options

How It Works

Privacy & data flow

Requirements

License