Xserver MCP
Related Servers
Alternatives to Xserver MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA read-only MCP server that gives Claude Code secure, non-invasive access to infrastructure logs, service status, metrics, Ansible facts, and Docker state via SSH, with a strict command allowlist and no write operations.-
- AlicenseAqualityBmaintenanceAn MCP server that lets Claude monitor and manage a TrueNAS box in plain English. It is deliberately read-only, providing tools to check alerts, storage pools, snapshots, services, and more.181MIT
- FlicenseNot gradedqualityBmaintenanceA read-only, OAuth 2.1-authenticated MCP server that lets Claude inspect the live state of a self-hosted server — system resources, containers, service and website health, n8n automations, video jobs, backups, repositories, error summaries, a component design system, uptime monitoring, and its own audit trail. All twenty-one tools are strictly observation-only, with no shell, file browser, SQL console, or Docker socket, so nothing can be started, stopped, deployed, or deleted.-
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that enables Claude Code to access MySQL databases, allowing safe querying with SELECT, SHOW, DESCRIBE, and EXPLAIN.22 npmMIT

masaro-infra-mcpofficial
FlicenseNot gradedqualityCmaintenanceA secure MCP server providing read-only tools to interact with Cloudflare, Coolify, and other infrastructure services, enabling AI clients to safely diagnose and validate environments.-- AlicenseNot gradedqualityCmaintenanceAn MCP server implementation that enables Claude to execute read-only queries against MariaDB databases and explore database schemas through natural language.20MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: endpoints discovery, account info, server status, resource listing, and generic GET. There is no overlap, and the generic GET is reserved for uncovered endpoints.
All tool names follow a consistent pattern: 'xserver_' prefix with lowercase and underscores. The names use a mix of nouns (endpoints, account_info, server_status) and verbs (list, get), but the convention is uniform.
Five tools is appropriate for the scope of the server, covering essential read-only operations for the XServer API without being excessive or insufficient.
The toolset provides near-complete read-only coverage, including account info, server status, resource listing, and a generic GET for missing endpoints. A minor gap is the lack of support for write operations, but that is by design.