Skip to main content
Glama
john-broadway

Proximo

by john-broadway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Proximo

  • ProxmoxMCP-Plus

    RekklesNA
    A
    license
    Not graded
    quality
    A
    maintenance
    An enhanced Python-based MCP server that enables complete VM lifecycle management and monitoring of Proxmox virtualization platforms through natural language, with 11 REST API endpoints for seamless integration.
    3,181 PyPI
    567
    MIT

Related Servers

  • proxmox-mcp-server

    edasan0568
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables management of Proxmox VE environments via the Proxmox API, including node listing, guest management, and VM/LXC creation with Cloud-Init.
    -

  • ProxmoxMCP-Plus

    rodaddy
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables comprehensive management of Proxmox virtualization environments, including VM and container lifecycle, snapshots, backups, monitoring, and OpenAPI integration.
    14
    MIT

  • PVE MCP Server

    gneely74
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables managing Proxmox Virtual Environment resources including VMs, containers, storage, cluster status, nodes, and tasks.
    -

  • Proxmox MCP Server

    thanhan92-f1
    A
    license
    Not graded
    quality
    A
    maintenance
    Exposes 338 tools for the Proxmox Virtual Environment API, enabling users to inspect and control nodes, QEMU VMs, LXC containers, storage and backups, clustering and HA, users and permissions, firewall rules, disks, Ceph, ACME certificates, SDN, notifications, and resource pools. Includes lifecycle actions, snapshots, migration, metrics, task tracking, and guest-agent command execution, with an optional read-only mode that blocks all writes.
    MIT
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

A4/5.0

Scored across 7 tools

Disambiguation4/5

The set is largely distinct: audit_entries reads vs audit_verify proves the ledger, and proximo_find_tools carries explicit steering to prefer proximo_recall for estate questions. The main soft spot is proximo_call vs proximo_read, which overlap in purpose and rely on the mutating/read-only distinction in descriptions to separate them.

Naming Consistency4/5

Names are snake_case throughout with clear domain prefixes (audit_* for ledger, proximo_* for the facade), which is readable and predictable. The verb/noun pattern varies a bit (find_tools, tool_schema, call, read are not uniform verb_noun), but no chaotic mixing.

Tool Count5/5

Seven tools is well-scoped for a facade that fronts 900+ hidden tools, and each earns its place: discovery, schema lookup, two execution paths, memory recall, and audit read/verify. No bloat and no obvious redundancy in count.

Completeness4/5

The surface covers the full gateway lifecycle: find tools, get schema, execute (read or call), recall estate memory, and read/verify the audit ledger. Minor gap is no explicit list-all or paginated catalog browsing beyond keyword search, but agents can work around it.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources