Skip to main content
Glama
Sign In
LerianStudio

Lerian MCP Server

by LerianStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Lerian MCP Server

No user-submitted related servers found.

    Related Servers

    • LaserData Docs MCP by laserdata

      LaserData Docs MCPofficial

      laserdata
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to answer Laser SDK and LaserData Cloud questions from current documentation instead of training data, drawing on both the guides website and the public Python API surface. It provides ranked search, full-page retrieval, code example discovery, and related-page navigation across both corpora.
      8
      Apache 2.0

    • natural-docs-mcp

      jsharma103
      A
      license
      A
      quality
      D
      maintenance
      Provides read-only tools to search, read, and look up Natural API documentation from an AI agent, enabling documentation lookup without credentials.
      4
      MIT

    • @octri/mcp

      OctriDev
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.
      7
      71 npm
      3
      MIT

    • Theneo MCP Server

      atombreak
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automatically create, update, and publish API documentation through Theneo's platform. Supports OpenAPI specs, Postman collections, AI-powered description generation, and natural language interactions for seamless documentation workflows.
      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

    A3.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each product-specific tool clearly targets a distinct product, and the discover/execute split is unambiguous. The two meta tools (lerian and portfolio-workflow) serve separate discovery and cross-product workflow purposes, so there is no overlap or confusion between any tools.

    Naming Consistency4/5

    The 14 product tools follow a highly consistent <product>-discover/<product>-execute pattern. However, the 'lerian' and 'portfolio-workflow' tools deviate from this convention, introducing a minor inconsistency that prevents a perfect score.

    Tool Count4/5

    With 16 tools, the count is slightly above the typical 3-15 range, but every tool is necessary to cover seven distinct products, each requiring discovery and execution, plus two meta tools. The size is justified by the multi-product scope.

    Completeness5/5

    The tool set provides complete coverage for each product with both discovery and execution capabilities, including full CRUD operations. The addition of a unified documentation tool and a cross-product workflow tool ensures no dead ends and covers the entire lifecycle from exploration to execution.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources