Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

Related Servers

Alternatives to Local Utilities MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      A general-purpose MCP server providing time-related utilities such as fetching current time, Unix timestamps, and formatting services. It supports both local stdio and remote SSE communication modes for versatile AI client integration.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A self-contained, dependency-free MCP server that provides utility tools for time, date, mathematical calculations, and shell command execution. It supports remote connectivity through SSE and is designed for easy deployment via Docker.
      GPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server with 30+ custom tools organized into categories: date/time operations, file management, system information, text processing, and web operations. Enables async communication with robust error handling and flexible CLI integration.
      31
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A simple MCP server that provides basic utility tools for text manipulation, file operations, and calculations, intended to be connected to Claude AI desktop app.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Lightweight MCP server providing system time tools (current time, date, datetime, time components, unix timestamp) for LLM applications.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A lightweight Node.js MCP server with zero dependencies offering 9 built-in tools for system info, web fetching, GitHub search, file operations, shell execution, and key-value memory, enabling AI agents to perform these tasks via the Model Context Protocol.
      -

    TDQS

    C2.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct name and purpose, even though some lack descriptions. The 'get_*' tools clearly differentiate between hostname, node version, public IP, time/date, and thoughts, while 'list_directory', 'check_port', and the thought management tools are all distinct.

    Naming Consistency5/5

    All tool names follow a consistent lowercase_snake_case pattern, predominantly using verb_noun structure (e.g., 'get_hostname', 'list_directory', 'clear_thoughts'). The single verb 'think' is a minor deviation but still fits the pattern.

    Tool Count5/5

    10 tools is a reasonable number for a local utilities server, covering both system information and a thought management module without overloading the surface.

    Completeness3/5

    The thought management tools are complete, but the system utilities are sparse, lacking common operations like disk space, CPU usage, or process listing. This leaves notable gaps for a 'Local Utilities' server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues