Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lcm2m-caddis-mcp

No user-submitted related servers found.

    Related Servers

    • Generic Database MCP Server

      bleckcorp
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only SQL querying and schema inspection across MSSQL, PostgreSQL, and MySQL databases via MCP tools.
      -

    • PostgreSQL-MCP-Server

      I8Zoro8I
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to safely query one or more PostgreSQL databases with read-only tools and explicitly approved write operations.
      56 npm
      1
      MIT

    • jisr-mcp

      Gamaleldientarek
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to securely access Jisr's documented HR Open API read-only operations, including employees, attendance, leave, payroll, finance, and discovery tools, with role-based field policies and dual protocol support.
      11
      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.6/5.0

    Scored across 31 tools

    Disambiguation5/5

    All tools have clearly distinct purposes: get vs list for single vs multiple entities, and specialized tools like caddis_get_tree for hierarchy, caddis_batch for batching. Descriptions explicitly guide when to use each one, minimizing confusion.

    Naming Consistency5/5

    All tools follow the consistent pattern 'caddis_<verb>_<noun>' with snake_case. Verbs are uniformly 'get' for single entities and 'list' for multiple, with only minor outliers like 'caddis_get_tree' and 'caddis_batch' that still fit the pattern.

    Tool Count3/5

    31 tools is on the high side, exceeding the typical recommended range of 3-15. However, the domain of manufacturing monitoring is rich and warrants many specialized queries. The count is justified but still feels heavy; it's borderline between 2 and 3.

    Completeness3/5

    The server covers a wide range of read-only operations for equipment, org units, alarms, tags, runs, etc. However, it lacks any write operations (create, update, delete), which is a notable gap if full lifecycle management is expected. For a read-only monitoring API, it is reasonably complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources