Skip to main content
Glama
Sign In
lyra-mcp

lyra-mcp

by Ralf090102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lyra-mcp

No user-submitted related servers found.

    Related Servers

    • ragdoc-mcp

      Rajagopalhertzian
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to locally build, tune, and debug retrieval pipelines by parsing technical documents, indexing content, retrieving and reranking results, diagnosing failures, planning pipelines, and evaluating output quality.
      2
      MIT

    • Qdrant RAG Build

      avaazquezz
      A
      license
      A
      quality
      B
      maintenance
      Enables users to build and manage a complete retrieval-augmented generation pipeline through conversation, including file ingestion, collection management, hybrid search, reranking, citations, and a guided setup wizard.
      33
      Apache 2.0

    • AgentOps EvalBench MCP

      AbhinavVarma02
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM evaluation and observability by uploading documents, building test sets, running RAG pipelines, and automatically scoring answers for groundedness, hallucination risk, retrieval quality, latency, and cost, with tools exposed to MCP-compatible clients.
      1
      MIT

    • ico-mcp

      apriori3d
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to search and compose typed operators into validated, runnable pipelines, propose missing operators or types as drafts, and crystallize proven drafts into stable operators through a human-reviewed GitHub pull request.
      40 PyPI
      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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct: list_stages is for discovery, get_stage_config for targeted reads, set_stage_config for persistent writes, and the two run tools differ by scope. Minor overlap exists because list_stages already includes current config, making get_stage_config somewhat redundant.

    Naming Consistency5/5

    All tools follow a clean verb_noun snake_case pattern: list/get/set/run + object. The naming style is perfectly consistent across the set.

    Tool Count5/5

    Five tools is well-scoped for a pipeline stage configuration and execution server. Each tool covers a distinct operation without bloat or obvious missing essentials.

    Completeness4/5

    The surface covers stage discovery, config read/write, single-stage execution, and full-pipeline execution. A minor gap is that run_pipeline does not accept config_overrides, so one-off full-pipeline comparisons require temporarily mutating persistent config.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources