Skip to main content
Glama
Sign In
leo1394

oh-my-laya

by leo1394
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to oh-my-laya

No user-submitted related servers found.

    Related Servers

    • laya-mcp — on-device typed

      devthinker-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Laya-MLX as an MCP server (and plain-HTTP API). It answers typed decisions — choose an option / score a rubric / is this true? — on your own machine (Apple Silicon / MLX), with no cloud and ~10ms after warm-up. Not a chatbot. No token-by-token text, no JSON that can break. One forward pass returns a structured answer you can branch on. Ideal for routing, triage, classification, lead scoring, and g
      MIT

    • local-mcp

      jkjoplin
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables running MCP tools against local MLX models on your Mac, with hardware-aware configuration, CLI streaming, and a dashboard for routing and monitoring.
      7,040 npm
      -

    • decidealot

      psyb0t
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local typed decision-making over MCP Streamable HTTP, running Laya and Von models to turn arbitrary state into choice, score, and yes/no answers with probabilities.
      3
      Do What The F*ck You Want To Public
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation4/5

    laya_tell_me runs a typed decision while laya_advisor_preferences reads/saves configuration policy, so their core purposes are distinct. The shared 'advisor' vocabulary and overlapping policy/recommendation language create minor potential confusion, but an agent can tell them apart.

    Naming Consistency3/5

    Both names use a consistent laya_ snake_case prefix, which is good. However the second element is inconsistent in style: laya_tell_me is an imperative verb phrase while laya_advisor_preferences is a noun phrase, breaking a predictable pattern.

    Tool Count3/5

    Two tools is thin for a server that apparently covers decision execution, model catalog advice, policy configuration, and squad setup. Much functionality appears overloaded into these two, which is borderline rather than comfortably scoped.

    Completeness3/5

    The domain (advisory decisions plus preference management) seems approximated by running decisions and configuring policy. There is no separate operation to inspect models, ceilings, or squad state independently, so several capabilities are only reachable indirectly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources