Skip to main content
Glama
microdotdo

micro-mcp

by microdotdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to micro-mcp

No user-submitted related servers found.

    Related Servers

    • mcponce

      litepacks
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables building and running MCP servers from a single executable, with shared daemons, concurrency controls, retries, caching, security, and OpenAPI integration.
      84 npm
      MIT

    • heddle

      goweft
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to define and run MCP tools using declarative YAML configs with built-in trust enforcement, credential brokering, and tamper-evident audit logging.
      14
      MIT
    • mcp-servers by DXHeroes

      mcp-serversofficial

      DXHeroes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables deploying standalone MCP connectors, discovering them through a validated catalog, and running an optional trusted polyglot runtime for the DX Heroes MCP Gateway.
      Apache 2.0
    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.5/5.0

    Scored across 68 tools

    Disambiguation4/5

    Most tools are scoped to a distinct resource—domains, members, schedules, backups, retention, users—and the plural-list vs singular-action naming helps separate reads from mutations. A few generic status/logs/usage tools overlap in scope, but their descriptions clearly distinguish project status, account usage, platform status, and local runner logs.

    Naming Consistency4/5

    All tools share the micro_ prefix and snake_case, and mutations mostly follow a consistent resource_action pattern such as domain_add, member_remove, and backup_restore. Minor deviations like bare-verb tools (doctor, remix, pull, rollback) and noun-only read tools keep it from being perfectly uniform.

    Tool Count1/5

    68 tools is far beyond the well-scoped 3-15 range and is an extreme surface for a single MCP server, even for a broad platform. This will tax context windows and make tool discovery harder; several status, usage, and billing tools could likely be consolidated.

    Completeness4/5

    The surface covers most lifecycle operations across domains, members, invitations, schedules, backups, deployments, users, retention, and platform state, with create/read/update/delete coverage for major resources. Minor gaps remain—no file delete, no product delete/archive, no record create/update—so it is not a perfect 5.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources