Skip to main content
Glama
theluckystrike

mcp-maintenance-log

Related Servers

Alternatives to mcp-maintenance-log

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables voice-first household maintenance tracking, turning spoken updates into durable records, service history, and due-date reminders for a concise maintenance brief.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables trades and field service work to be tracked per job: logging labor hours at worker rates and materials used, keeping running totals in integer cents per currency, and moving each job through a status machine from open to invoiced or archived. It also produces daily or weekly summaries of hours and value, and renders a printable card with a signature line for client sign-off.
      11
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Snipe-IT inventory systems through comprehensive asset and consumable operations. Supports creating, updating, tracking, and managing IT assets, consumables, maintenance records, file attachments, and generating labels.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables household maintenance planning and tracking through MCP tools, including reviewed step-by-step guides, command-driven state updates, and iCalendar generation for completed routines.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to track unpaid invoices and generate an escalating ladder of payment-reminder letters — first reminder, second reminder, and final notice — anchored to the due date, plus overdue listings, aging buckets, and a daily chase list of what to send today. It records payments and letters sent, rendering each letter as Markdown or printable HTML without ever emailing anything itself.
      11
      MIT

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation: adding/removing assets, logging maintenance, checking due items, reading history, exporting, and license management. There is no realistic confusion between them, and overlapping read features are separated clearly by scope.

    Naming Consistency3/5

    The names use clear prefixes but mix noun-style and verb-style endings: asset_add and maintenance_export are verb-like, while asset_history, maintenance_due, and license_status are noun-like. The pattern is readable and predictable by prefix, but not fully consistent.

    Tool Count5/5

    Eight tools is well-scoped for a maintenance-log server: six cover the core asset/maintenance workflow and two cover licensing. Each tool has a clear purpose and none feel redundant.

    Completeness4/5

    The core lifecycle is covered: assets can be added, logged against, inspected, reported on, exported, and removed. Minor gaps include no way to update asset metadata or delete/correct an individual maintenance log entry, but agents can still complete primary workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues