Skip to main content
Glama
Sign In
Red5d

Beszel MCP Server

by Red5d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Beszel MCP Server

No user-submitted related servers found.

    Related Servers

    • pocketbase-mcp

      Touexe
      F
      license
      A
      quality
      B
      maintenance
      Enables managing PocketBase instances through intent-first tools for schema inspection, record CRUD, bulk operations, authentication, file handling, and server monitoring, with optional destructive operations gated behind explicit opt-in.
      11
      12
      -

    • PocketBase MCP Server

      tyoon33725
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to run advanced operations against a PocketBase backend, including creating and inspecting collections, CRUD on records with filtering and pagination, user authentication and account creation, and database backups. It also supports local stdio and Docker-based deployment with admin credentials configured via environment variables.
      37 npm
      ISC

    • PocketBase MCP Server

      LEX-lib
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing a PocketBase instance from chat by exposing 30+ tools for collections, records, authentication, files, logs, settings, backups, crons, health checks, and raw API requests. Works with Claude Desktop, Cursor, OpenCode, and other MCP-compatible clients.
      37 npm
      MIT

    • PocketBase MCP Server

      MomokaRichter
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables sophisticated interaction with PocketBase databases through the Model Context Protocol, including collection schema creation and retrieval, record CRUD with filtering, pagination and relationship expansion, user authentication and account management, and database backups. It can run locally or in Docker with configurable URL and admin credentials.
      37 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: list_alert_history retrieves historical records, list_alerts shows configurations, list_containers and list_systems enumerate monitored entities, and query_container_stats/query_system_stats fetch specific time-series data. The descriptions make it unambiguous which tool to use for each task.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case: list_alert_history, list_alerts, list_containers, list_systems, query_container_stats, and query_system_stats. The naming convention is predictable and readable throughout the set.

    Tool Count5/5

    With 6 tools, this server is well-scoped for monitoring systems and containers, covering listing entities and querying statistics. Each tool earns its place without being too sparse or bloated, fitting typical MCP server ranges.

    Completeness4/5

    The toolset provides solid read-only coverage for monitoring: listing alerts, containers, systems, and querying their stats. Minor gaps exist, such as no tools to create/update/delete alerts or containers, but agents can work around this for observation-focused workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources