Mongodb MCP Server vs MCP Victorialogs
A side-by-side look at the Mongodb MCP Server and MCP Victorialogs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mongodb MCP Server for databases work as a local process; choose MCP Victorialogs for databases over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mongodb MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MDB_MCP_CONNECTION_STRING. - You want tools like
aggregate, aggregate-db, collection-indexes.
Choose MCP Victorialogs when
- You need dedicated capabilities in the Databases domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
VL_INSTANCE_ENTRYPOINT, VL_INSTANCE_BEARER_TOKEN, VL_INSTANCE_HEADERS, MCP_PASSTHROUGH_HEADERS, VL_DEFAULT_TENANT_ID, MCP_SERVER_MODE, MCP_LISTEN_ADDR. - You want tools like
documentation, facets, field_names.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 65/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | MDB_MCP_CONNECTION_STRING | VL_INSTANCE_ENTRYPOINTVL_INSTANCE_BEARER_TOKENVL_INSTANCE_HEADERSMCP_PASSTHROUGH_HEADERSVL_DEFAULT_TENANT_IDMCP_SERVER_MODEMCP_LISTEN_ADDR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,149 | 104 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 53 | 13 |
| Full listing | View Mongodb MCP Server | View MCP Victorialogs |
Tools & capabilities
Mongodb MCP Server tools 53
aggregateRun an aggregation against a MongoDB collectionaggregate-dbRun an aggregation against a MongoDB databasecollection-indexesDescribe the indexes for a collectioncollection-schemaDescribe the schema for a collectioncollection-storage-sizeGets the size of the collectionconnectConnect to a MongoDB instancecountGets the number of documents in a MongoDB collection using db.collection.count() and query as an optional filter parametercreate-collectionCreates a new collection in a database. If the database doesn't exist, it will be created automatically.create-indexCreate an index for a collectiondb-statsReturns statistics that reflect the use state of a single databasedelete-manyRemoves all documents that match the filter from a MongoDB collectiondisconnectClose a MongoDB connection and revoke its connectionId.- +41 more on the listing page
MCP Victorialogs tools 13
documentationSearch documentation resources for the given search query, returning the URIs of the resources that match the search criteria sorted by relevance. This tool can help to get context for any VictoriaLogs related question.facetsThe most frequent values per each log field seen in the logs returned by the given <query> on the given [<start> ... <end>] time range. This tool uses `/select/logsql/facets` endpoint of VictoriaLogs API.field_namesGet field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name. This tool uses `/select/logsql/field_names` endpoint of VictoriaLogs API.field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/field_values` endpoint of VictoriaLogs API.flagsList of non-default flags (parameters) of the VictoriaLogs instance. This tools uses `/flags` endpoint of VictoriaLogs API.hitsThe number of matching log entries for the given <query> on the given [<start> ... <end>] time range grouped by <step> buckets. The returned results are sorted by time. This tool uses `/select/logsql/hits` endpoint of VictoriaLogs API.queryExecutes LogsQL query expression to search log entries. This tool uses `/select/logsql/query` endpoint of VictoriaLogs API.stats_queryLog stats for the given query at the given timestamp (time) in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query` endpoint of VictoriaLogs API.stats_query_rangeLog stats for the given query on the given [start ... end] time range with the given step interval. The stats is returned in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query_range` endpoint of VictoriaLogs API.stream_field_namesGet log stream field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name.. This tool uses `/select/logsql/stream_field_names` endpoint of VictoriaLogs API.stream_field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/stream_field_values` endpoint of VictoriaLogs API.stream_idsGet _stream_id values for the log streams from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every _stream_id. This tool uses `/select/logsql/stream_ids` endpoint of VictoriaLogs API.- +1 more on 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.
Mongodb MCP Server
{
"mcpServers": {
"mongodb-mcp-server": {
"command": "npx",
"args": [
"-y",
"mongodb-mcp-server@latest"
],
"env": {
"MDB_MCP_CONNECTION_STRING": "YOUR_MDB_MCP_CONNECTION_STRING_HERE"
}
}
}
}
MCP Victorialogs
{
"mcpServers": {
"victoriametrics-community-mcp-victorialogs": {
"url": "https://play-vmlogs-mcp.victoriametrics.com/mcp"
}
}
}
Frequently asked questions
Mongodb MCP Server is categorized under Databases and uses a local stdio subprocess. MCP Victorialogs belongs to Databases and uses a remote HTTP/SSE transport. Pick Mongodb MCP Server for databases work and MCP Victorialogs for databases.
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.
Mongodb MCP Server has no declared pricing — check the project's own site. MCP Victorialogs is listed as free. Auth: no auth required. 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 mongodb-mcp-server and victoriametrics-community-mcp-victorialogs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mongodb MCP Server has a quality signal of 65/100 (Great) with 1 views, 0 installs and 1,149 GitHub stars. MCP Victorialogs has 64/100 (Good) with 2 views, 0 installs and 104 GitHub stars.