MCP Victorialogs vs MCP Server
A side-by-side look at the MCP Victorialogs and MCP Server 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 monitoring work over a hosted endpoint; choose MCP Server for monitoring over a hosted endpoint. 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 Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- 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. - You want tools like
documentation, facets, field_names.
Choose MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
thinkneo_check_spend, thinkneo_complete, thinkneo_read_memory.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 63/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | VL_INSTANCE_ENTRYPOINTVL_INSTANCE_BEARER_TOKENVL_INSTANCE_HEADERSMCP_PASSTHROUGH_HEADERSVL_DEFAULT_TENANT_IDMCP_SERVER_MODE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 104 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 13 | 68 |
| Full listing | View MCP Victorialogs | View MCP Server |
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 Server tools 68
thinkneo_check_spendCheck AI spend summary for a workspace, team, or project. Returns real cost breakdown by provider, model, and time period from the ThinkNEO AI gateway.thinkneo_completeRun a governed LLM completion through the ThinkNEO AI gateway. The request is authorized, classified, and policy-checked against your workspace governance BEFORE any provider is called — a blocked prompt never reaches the model. Tenant/workspace are derived from your API key.thinkneo_read_memoryRead Claude Code project memory files. Without arguments, returns the MEMORY.md index listing all available memories. With a filename argument, returns the full content of that specific memory file. Use this to access project context, user preferences, feedback, and reference notes persisted across Claude Code sessions.thinkneo_write_memoryWrite or update a Claude Code project memory file (.md). Persists project context, user preferences, feedback, and reference notes across Claude Code sessions. Filename must end in .md with lowercase alphanumeric characters. Path traversal is blocked. Requires authentication.Use this to persist project context, user preferences, feedback, and reference notes across Claude Code sessions. The filename must end in .md and contain only lowercase letters, digits, underscores, and hyphens (e.g. 'user_fabio.md', 'project_new_feature.md'). Path traversal is blocked.thinkneo_evaluate_guardrailEvaluate a prompt or text against ThinkNEO guardrail policies before sending it to an AI provider. Returns risk assessment, violations found, and recommendations. Requires authentication.thinkneo_checkFree-tier prompt safety check. Analyzes text for prompt injection patterns and PII (credit card numbers, Brazilian CPF, US SSN, email, phone, passwords). Returns a safety assessment with specific warnings. No authentication required.thinkneo_check_policyCheck AI governance policies including model access, budget limits, data controls, and agent governance from the ThinkNEO gateway.thinkneo_get_budget_statusCheck AI budget status including spend vs limit, forecast, and chargeback data from the ThinkNEO gateway.thinkneo_list_alertsList active alerts for budget, policy, SLA, and security from the ThinkNEO gateway.thinkneo_get_compliance_statusGet compliance status including framework coverage (EU AI Act, ISO 42001, NIST AI RMF, SOC 2) and governance assessments from the ThinkNEO gateway.thinkneo_provider_statusGet real-time health and performance status of AI providers routed through the ThinkNEO gateway. Shows latency, error rates, and availability. No authentication required.thinkneo_schedule_demoSchedule a demo or discovery call with the ThinkNEO team. Collects contact information and preferences. No authentication required.- +56 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.
MCP Victorialogs
{
"mcpServers": {
"mcp-victorialogs": {
"url": "https://play-vmlogs-mcp.victoriametrics.com/mcp"
}
}
}
MCP Server
{
"mcpServers": {
"thinkneoai-mcp-server": {
"url": "https://mcp.thinkneo.ai/mcp"
}
}
}
Frequently asked questions
MCP Victorialogs is categorized under Monitoring and uses a remote HTTP/SSE transport. MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Victorialogs for monitoring work and MCP Server for monitoring.
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 has no declared pricing — check the project's own site. MCP Server is listed as freemium — a free tier with paid plans. Auth: api key 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 mcp-victorialogs and thinkneoai-mcp-server 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 63/100 (Good) with 1 views, 0 installs and 104 GitHub stars. MCP Server has 56/100 (Good) with 2 views, 0 installs and 3 GitHub stars.