Skip to main content
Glama
open-lzt

lzt-dev-mcp

by open-lzt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to lzt-dev-mcp

No user-submitted related servers found.

    Related Servers

    • lolzteam-mcp

      skallekss
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing access to Lolzteam Market and Forum APIs with 271 tools for account trading, forum interactions, and more.
      5
      MIT

    • amoCRM MCP Server

      cAIborg-ai
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that provides 36 tools for interacting with the amoCRM (Kommo) API v4, covering leads, contacts, companies, and tasks. It supports full entity lifecycles, account analytics, and bulk operations with integrated OAuth 2.0 and rate limiting.
      2
      MIT

    • iikoServer MCP Server

      simba87
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for iiko restaurant management system REST API, providing 39 tools to manage products, employees, entities, documents, payments, reports, and raw API access.
      1
      -

    • olx-mcp

      omznc
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the OLX.ba API that enables searching, publishing, editing, and managing listings (ads), including image handling, sponsorships, categories, locations, and user account operations through 36 tools covering all official API endpoints.
      4 npm
      6
      MIT

    • lol-client-mcp Public

      johnnyinlee
      A
      license
      C
      quality
      D
      maintenance
      An MCP (Model-Controller-Processor) server for accessing League of Legends client data. This server provides a collection of tools that communicate with the League of Legends Live Client Data API to retrieve in-game data.
      12
      12
      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

    B3.2/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools cleanly target distinct resources (flows, runs, subscriptions, schemas), but a few pairs could confuse an agent: list_methods vs describe_api both surface API catalog information, and get_method_schema vs get_dynamic_method both describe method inputs/outputs. Overall, descriptions and naming help separate the main workflows.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: list_*, get_*, create_*, import_*, export_*, send_*, poll_*, confirm_*, register_*. The naming is uniform across the pylzt, lzt-flow, and lzt-eventus subdomains, making the tool set predictable and easy to navigate.

    Tool Count4/5

    At 29 tools, this is on the heavier side, but the server covers three distinct subsystems (pylzt, lzt-flow, lzt-eventus), each with a reasonable set of operations. The count feels justified for the stated purpose, though a few introspection helpers could potentially be consolidated.

    Completeness4/5

    The server provides strong lifecycle coverage: flows can be listed, created, imported, exported, compiled, and run; subscriptions can be created, listed, polled, and confirmed; API introspection covers methods, schemas, rate limits, and errors. Minor gaps like updating or deleting flows/subscriptions exist, but agents can likely work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources