Skip to main content
Glama
BxNxM
by BxNxM

Related Servers

Alternatives to micrOSMCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A demonstration MCP server built in TypeScript that shows how to implement stdio-based communication for integration with MCP clients. Serves as a template for building custom MCP servers with strong typing and maintainability.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Production-ready TypeScript MCP server exposing utility, GitHub, and Microsoft Teams tools over stdio.
      14
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables building and running an MCP server with automatically discovered tools, prompts, and resources over HTTP or STDIO, using TypeScript and Zod schemas.
      -
    • F
      license
      A
      quality
      C
      maintenance
      Enables users to run a modular TypeScript MCP server that communicates over STDIO and exposes tools for summing numbers and greeting users.
      2
      -

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role, but list_devices and discover_devices both show device inventories, and search_devices and discover_commands both surface command signatures. The descriptions clarify the differences (known vs. live scan, indexed vs. live query), so selection should be reliable.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern (list_devices, discover_commands, discover_devices, run_command, search_devices, set_device_note). The two discover_* tools are differentiated by their object, maintaining clarity.

    Tool Count5/5

    Six tools is well-scoped for a device management server, covering discovery, inventory, command lookup, execution, and note-taking without unnecessary bloat. Each tool earns its place.

    Completeness5/5

    The tool surface covers the full lifecycle of interacting with micrOS devices: discovering devices on the network, listing known devices, searching for capabilities, learning command signatures, executing commands, and annotating device context. No obvious dead ends or missing core operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues