Hindsight vs Yandex Delivery MCP
A side-by-side look at the Hindsight and Yandex Delivery MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hindsight for knowledge & memory work as a local process; choose Yandex Delivery MCP for delivery as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hindsight when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HINDSIGHT_API_LLM_API_KEY.
Choose Yandex Delivery MCP when
- You need dedicated capabilities in the Delivery domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YANDEX_DELIVERY_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Delivery |
| Quality signal | 57/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | HINDSIGHT_API_LLM_API_KEY | YANDEX_DELIVERY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 51,891 | 0 |
| Directory activity | 13 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hindsight | View Yandex Delivery MCP |
Tools & capabilities
Hindsight tools
No tool names declared yet. Check the project README from the listing page.
Yandex Delivery MCP 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.
Hindsight
{
"mcpServers": {
"vectorize-io-hindsight": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/hindsight-coding-agents"
],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE"
}
}
}
}
Yandex Delivery MCP
{
"mcpServers": {
"yandex-delivery-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-dostavka@latest"
],
"env": {
"YANDEX_DELIVERY_TOKEN": "YOUR_YANDEX_DELIVERY_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Hindsight is categorized under Knowledge & Memory and uses a local stdio subprocess. Yandex Delivery MCP belongs to Delivery and uses a local stdio subprocess. Pick Hindsight for knowledge & memory work and Yandex Delivery MCP for delivery.
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.
Hindsight is listed as free. Auth: api key required. Yandex Delivery MCP has no declared pricing — check the project's own site. 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 vectorize-io-hindsight and yandex-delivery-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hindsight has a quality signal of 57/100 (Good) with 13 views, 0 installs and 51,891 GitHub stars. Yandex Delivery MCP has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.