Server Everything vs Yandex Delivery MCP
A side-by-side look at the Server Everything 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 Server Everything for other tools and integrations 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 Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
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 | Other Tools and Integrations | Delivery |
| Quality signal | 73/100 · Great | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | YANDEX_DELIVERY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91,405 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Server Everything | View Yandex Delivery MCP |
Tools & capabilities
Server Everything tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
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
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Yandex Delivery MCP belongs to Delivery and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.
Server Everything is listed as free. Auth: no auth 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 modelcontextprotocol-server-everything and yandex-delivery-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 9 views, 0 installs and 91,405 GitHub stars. Yandex Delivery MCP has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.