Trieve vs TenderHunt
A side-by-side look at the Trieve and TenderHunt MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TenderHuntSearch & Data Extraction · Remote HTTP/SSEBelarus public tenders: search, analytics, docs, and alerts via TenderHunt agent.39FairAuth: oauth 2.0Verdict: choose Trieve for search & data extraction work as a local process; choose TenderHunt for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Trieve when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TRIEVE_API_KEY, TRIEVE_ORGANIZATION_ID, TRIEVE_DATASET_ID. - You want tools like
search.
TChoose TenderHunt when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TenderHunt | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 61/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | TRIEVE_API_KEYTRIEVE_ORGANIZATION_IDTRIEVE_DATASET_ID | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,721 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Trieve | View TenderHunt |
Tools & capabilities
Trieve tools 1
searchSearch through Trieve datasets using semantic, fulltext, hybrid or BM25 search with advanced filtering and highlighting options
TenderHunt tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Trieve
{
"mcpServers": {
"devflowinc-trieve": {
"command": "npx",
"args": [
"trieve-mcp-server@latest"
],
"env": {
"TRIEVE_API_KEY": "YOUR_TRIEVE_API_KEY_HERE",
"TRIEVE_ORGANIZATION_ID": "YOUR_TRIEVE_ORGANIZATION_ID_HERE",
"TRIEVE_DATASET_ID": "YOUR_TRIEVE_DATASET_ID_HERE"
}
}
}
}
TenderHunt
{
"mcpServers": {
"tenderhunt": {
"command": "npx",
"args": [
"-y",
"tenderhunt"
]
}
}
}
Frequently asked questions
Trieve is categorized under Search & Data Extraction and uses a local stdio subprocess. TenderHunt belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick Trieve for search & data extraction work and TenderHunt for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Trieve is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. TenderHunt has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add devflowinc-trieve and tenderhunt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Trieve has a quality signal of 61/100 (Good) with 3 views, 0 installs and 2,721 GitHub stars. TenderHunt has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.