Skip to main content
Glama
Michael-Drake

io.github.Michael-Drake/rentctl

by Michael-Drake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.Michael-Drake/rentctl

No user-submitted related servers found.

    Related Servers

    • Paddock

      igbaryya
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to manage local development environments over MCP by starting, stopping, and restarting applications and processes, reading logs with cursors, and inspecting or freeing listening ports. Exposes a fixed set of id- and port-based tools, so the agent can operate registered processes without running arbitrary commands.
      2 npm
      MIT

    • pi-agent-mcp

      a809384377
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts like Claude Code and Codex to spawn, manage, and interact with persistent, reusable Pi coding-agent sessions, supporting task dispatch, status checks, and session lifecycle control.
      2 npm
      -

    • Coding Tools MCP

      cuishihui66
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives any MCP-compatible AI chat or agent a safe, model-neutral coding runtime with file read/search, structured multi-file patches, command execution, interactive sessions, and git operations, all confined to a single workspace and gated by permission modes.
      Apache 2.0

    • pokeclaw

      madebydia
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    env_up (start/renew) and env_down (release) are clearly opposed, and env_ls (list inventory) versus env_sweep (reconcile leases) are distinguishable, though an agent could plausibly reach for env_sweep when it means env_down since both stop environments. The descriptions do enough work to keep boundaries clear.

    Naming Consistency4/5

    All four names use snake_case with a consistent env_ prefix, so the family is immediately recognizable. The action tokens mix directional (up/down) with verb/CLI-style (ls/sweep) forms, a minor deviation from a strict verb_noun pattern but still readable.

    Tool Count4/5

    Four tools is a tight, plausible set for a lease manager covering start, release, inventory, and reconciliation, with no obvious filler. It sits at the low end of the recommended range, and a dedicated status/logs tool could arguably earn a fifth slot.

    Completeness3/5

    The core lifecycle (start, stop, list, reconcile) is covered, but there is no way to fetch logs for a specific environment even though errors reference log_tail, and no single-environment status/get beyond the full inventory listing. These are workable-but-notable gaps for debugging failed starts.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources