MCP Victorialogs vs MCP Sqlite
A side-by-side look at the MCP Victorialogs and MCP Sqlite MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Victorialogs for databases work over a hosted endpoint; choose MCP Sqlite for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose MCP Sqlite when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
db_info, query, list_tables.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 64/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | VL_INSTANCE_ENTRYPOINTVL_INSTANCE_BEARER_TOKENVL_INSTANCE_HEADERSMCP_PASSTHROUGH_HEADERSVL_DEFAULT_TENANT_IDMCP_SERVER_MODEMCP_LISTEN_ADDR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 104 | 131 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 13 | 8 |
| Full listing | View MCP Victorialogs | View MCP Sqlite |
Tools & capabilities
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
MCP Sqlite tools 8
db_infoGet information about the SQLite database including path, existence, size, and table countqueryExecute a raw SQL query against the database with optional parameter valueslist_tablesList all user tables in the SQLite database (excludes system tables)get_table_schemaGet the schema information for a specific table including column detailscreate_recordInsert a new record into a table with specified dataread_recordsRead records from a table with optional conditions, limit, and offsetupdate_recordsUpdate records in a table based on specified conditionsdelete_recordsDelete records from a table based on specified conditions
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.
MCP Victorialogs
{
"mcpServers": {
"victoriametrics-community-mcp-victorialogs": {
"url": "https://play-vmlogs-mcp.victoriametrics.com/mcp"
}
}
}
MCP Sqlite
{
"mcpServers": {
"jparkerweb-mcp-sqlite": {
"command": "npx",
"args": [
"-y",
"mcp-sqlite"
]
}
}
}
Frequently asked questions
MCP Victorialogs is categorized under Databases and uses a remote HTTP/SSE transport. MCP Sqlite belongs to Databases and uses a local stdio subprocess. Pick MCP Victorialogs for databases work and MCP Sqlite 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.
MCP Victorialogs is listed as free. Auth: no auth required. MCP Sqlite 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 victoriametrics-community-mcp-victorialogs and jparkerweb-mcp-sqlite as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Victorialogs has a quality signal of 64/100 (Good) with 2 views, 0 installs and 104 GitHub stars. MCP Sqlite has 65/100 (Great) with 4 views, 0 installs and 131 GitHub stars.