Skip to main content
Glama
Sign In
Proximo

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.
    2,693 PyPI
    650
    MIT

Related Servers

  • PVEHub-MCP

    EndlessSnake06
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables management of Proxmox VE and Proxmox Backup Server through curated and generic REST API tools, plus opt-in shell access to hosts, LXC containers, QEMU VMs, and PBS hosts under rights-aware, policy-controlled, audited access.
    MIT

  • 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.
    12
    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.
    -

  • pvemcp

    yutho-o
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to inspect and control Proxmox VE clusters through the full API, with optional SSH/LXC command execution, read-only by default and writes gated behind explicit authorization.
    1
    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

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

The core split (find = discover addresses, plan = dry-run verdict, read = GET, call = mutate, audit = ledger) is clear and each tool has a distinct role. The one soft spot is that proximo_read also accepts plain words while proximo_find exists specifically to resolve words to addresses, and proximo_plan also reads current state, which could cause a misselection.

Naming Consistency4/5

Names follow a predictable prefix_action pattern (proximo_read/call/find/plan, audit_entries/audit_verify), which is easy to scan. Minor deviation: audit_entries uses a noun while the others use verbs, splitting the set into two prefixes, but readability is unaffected.

Tool Count5/5

Six tools is well-scoped for a governed API client: one each for discovery, read, plan, mutate, and two for audit integrity. No tool appears redundant or vestigial.

Completeness5/5

The surface covers the full lifecycle: discovery (proximo_find), schema/verdict inspection (proximo_plan), reads (proximo_read), mutations with plan-first safety and undo (proximo_call), plus ledger inspection and chain verification (audit_entries/audit_verify). No obvious dead ends for the stated purpose.

Maintenance

ActivityActive
ResponsivenessUsually handled

Resources