Skip to main content
Glama
Sign In
lws-mcp

lws-mcp

by NKSTUD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to lws-mcp

No user-submitted related servers found.

    Related Servers

    • Logto MCP Server

      kdunin
      A
      license
      B
      quality
      B
      maintenance
      Enables managing Logto resources (users, applications, organizations, roles) via MCP clients like Cursor or Claude Desktop.
      26
      1
      MIT

    • Taskade MCP Server

      kevindeluca27194
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients such as Claude, Cursor, VS Code, and Windsurf to read and manage workspaces, projects, tasks, and AI agents, and to build automations through natural language. It also includes an OpenAPI codegen that turns any OpenAPI spec into MCP tools.
      1,866 npm
      MIT
    • ZopDev MCP

      ZopDev MCPofficial

      zopdev
      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

    • Corben MCP Server

      gatordevin
      A
      license
      Not graded
      quality
      D
      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.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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 recent community issues

    Resources