Skip to main content
Glama
Sign In
sanjeevkkansal

solfleet

by sanjeevkkansal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to solfleet

No user-submitted related servers found.

    Related Servers

    • Flotilla by paipaiio

      Flotillaofficial

      paipaiio
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage an entire fleet of servers over SSH through MCP, fanning a single intent out across many hosts with target expressions while enforcing a policy engine, approval gates, and tamper-evident audit logs. Supports rolling execution with circuit breakers, cross-host diffing, bulk file transfer, tmux sessions, and YAML workflows.
      23 npm
      17
      AGPL 3.0

    • vyne-mcp

      rajgoesout
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for vyne, a Solana DeFi automation engine, enabling creation, testing, and monitoring of multi-step workflows via 32 tools, 11 resources, and guided prompts.
      -

    • mia

      akadorkin
      A
      license
      B
      quality
      C
      maintenance
      Enables an agent to oversee and operate a fleet of Linux servers over the system ssh and Tailscale — inspecting host status, auditing configuration, tracking drift and reading history across many machines. Every mutating operation runs as a dry-run plan first and only applies after explicit confirmation of that exact plan, rolling out one host at a time with a local journal.
      63
      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 15 tools

    Disambiguation5/5

    Each tool targets a distinct operation (e.g., provisioning, upgrading, DNS management, health checks) with no overlapping purposes. Even related tools like plan_node_upgrade and upgrade are clearly separated by dry-run vs execution.

    Naming Consistency4/5

    All names use snake_case and are descriptive, but they mix verb-initial (e.g., bootstrap_builder_host, plan_node_upgrade) and noun-initial patterns (e.g., dns_pool_eject, fleet_status). This minor inconsistency does not hinder readability.

    Tool Count5/5

    15 tools is well-scoped for a fleet management server covering provisioning, upgrades, DNS, monitoring, and auditing. Each tool serves a clear purpose without redundancy.

    Completeness4/5

    Core lifecycle operations (provision, upgrade, restart, DNS management) are covered, but a decommission tool is missing. Minor gap considering the server's scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources