Skip to main content
Glama
caseSHY

caseSHY/aicoreutils

by caseSHY
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to caseSHY/aicoreutils

No user-submitted related servers found.

    Related Servers

    • local-mcp

      fan-67
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.
      2,994 npm
      MIT

    • Pare

      Dave-London
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides MCP servers that wrap common developer tools (git, npm, docker, etc.) returning structured JSON output, enabling AI agents to reliably interact with these tools without parsing fragile terminal text.
      7 npm
      138
      MIT

    • Cuba-Exec

      LeandroPG19
      A
      license
      A
      quality
      F
      maintenance
      Advanced shell command execution for AI agents — a Model Context Protocol (MCP) server with security policy engine, process lifecycle management, bounded output capture, POSIX signals, and token-efficient responses.
      6
      2
      Creative Commons Attribution Non Commercial 4.0 International

    • wrapmcp

      SubZtep
      A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.
      MIT

    • Modular MCP Server

      0brym
      F
      license
      B
      quality
      D
      maintenance
      A config-driven, zero-dependency MCP server with plugin architecture that enables filesystem operations, shell commands, HTTP requests, and utilities through simple JSON configuration.
      3
      1
      -
    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

    A4/5.0

    Scored across 100 tools

    Disambiguation4/5

    Tools are mostly distinct with clear descriptions, but there is slight overlap among hash tools (b2sum, sha256sum, hash) and file listing tools (ls, dir, vdir) that could cause minor confusion. Overall, each tool has a unique primary purpose.

    Naming Consistency3/5

    Most tools follow a single lowercase word naming convention (e.g., cat, sort, mkdir), but there are deviations like 'tool-list' and 'b2sum' that break the pattern. The verb_noun convention is absent, but the naming is predictable within the context of a coreutils clone.

    Tool Count1/5

    With 100 tools, the server is extremely over-scoped for an MCP server. Even though coreutils itself has many commands, exposing all of them as individual MCP tools creates an unwieldy surface that overwhelms agents and is far beyond the typical 3-15 tool range.

    Completeness5/5

    The tool surface is remarkably comprehensive for a coreutils server, covering file operations, text processing, system info, hashing, and process control. There are no obvious gaps given the domain; even standard commands like 'yes' and 'whoami' are missing but not critical. The set provides complete coverage for common CLI tasks.

    Maintenance

    ActivityStale
    ResponsivenessSyncing

    Resources