Skip to main content
Glama

Related Servers

Alternatives to lws-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      A
      maintenance
      Enables managing Logto resources (users, applications, organizations, roles) via MCP clients like Cursor or Claude Desktop.
      26
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and, when scoped writes are enabled, manage cloud estate data—inventory, costs, recommendations, schedules, governance, and deployments—across AWS, Azure, and GCP through a hosted remote MCP endpoint.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with 220+ tools for building websites, sending email, managing contacts, invoicing, databases, automation, and more through a single secure connection. Features hardware-bound authentication and works with Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients such as Claude, Cursor, VS Code, and Windsurf to list and manage workspaces, projects, tasks, AI agents, and automations through a hosted OAuth-secured endpoint or a local stdio package. Also generates MCP tools from any OpenAPI spec.
      1,439 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude, ChatGPT and other MCP clients to read an Amiqus ID account—clients, onboarding records and steps, check results, templates, case status counts and webhooks—and, when writes are enabled, create records.
      9
      MIT

    TDQS

    B3.4/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and descriptions clearly separate DNS zone inspection from propagation checks, contacts, hostings, and account/request operations. Minor overlap exists between add_dns_record and update_dns_record (upsert behavior) and between list_requests and list_pending_requests, but the descriptions largely resolve these.

    Naming Consistency5/5

    All tool names use consistent snake_case with a verb-noun pattern (get_, list_, create_, update_, delete_, set_, check_, request_). The convention is predictable across every resource area.

    Tool Count3/5

    26 tools is on the heavy side for an MCP surface; while the LWS domain is broad and each operation is granular, several tools could be consolidated (e.g., request listings, price lookups). The count is borderline rather than clearly excessive given the multi-service scope.

    Completeness2/5

    Core lifecycle operations are missing: there are no tools to register/renew/delete a domain, purchase/renew/delete a hosting, or delete a contact. The gap is especially pronounced because get_renewal_prices explicitly references renew_hosting, which does not exist, creating a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues