M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionVictoriaMetrics MCP ServerOfficial VictoriaMetrics MCP server for seamless integration with VictoriaMetrics API and documentation.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS69 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions15 / 2014 / 20
Maintenance16 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers and SREs using VictoriaMetrics for monitoring and observability.
  • Engineers who want to leverage AI assistants to simplify metric queries and operations.
  • Teams needing quick access to documentation and troubleshooting guides.
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users who do not use VictoriaMetrics; this server is not suitable for other monitoring systems.
  • Scenarios requiring write or modify operations, as the server only supports read-only APIs.
  • Environments sensitive to resource consumption, as the embedded documentation vector database may increase memory and CPU usage.
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Read access to VictoriaMetrics instance APIs (query, list metrics, export data, etc.).
  • If using Cloud mode, access to VictoriaMetrics Cloud API key.
  • Network access to connect to the VictoriaMetrics instance or Cloud service may be required.
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Need to carefully manage API tokens to avoid leaking sensitive data.
  • AI-generated queries and configurations may contain errors; should be verified before use in production.
  • The server may consume significant resources, especially when loading the documentation vector database; can save resources by disabling the documentation tool.
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Desktop, Cursor, Claude Code, Codex, VS Code, Zed, JetBrains IDEs, WindsurfClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools3015