Skip to main content
Glama
lanonasis

Lanonasis MCP Server

Official
by lanonasis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Lanonasis MCP Server

No user-submitted related servers found.

    Related Servers

    • Claude Memory MCP Server

      cbuntingde
      -
      license
      Not graded
      quality
      B
      maintenance
      Enterprise-grade MCP server for persistent, intelligent memory management across Claude Code sessions.
      -

    • Claude MCP Server Ecosystem

      Coder-RL
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server ecosystem providing Claude AI with 150+ specialized tools across enhanced memory, data analytics, security, design, and infrastructure domains with PostgreSQL, Redis, Qdrant, and Docker orchestration.
      -

    • memory-mcp

      User75621
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that stores project memory in Supabase, allowing AI tools to persist context, notes, and decisions across sessions. Enables Claude Code, Codex, and similar assistants to maintain long-term project continuity through persistent memory storage.
      2
      MIT

    • MCP Memory Server

      PlumyCat
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude persistent memory by storing conversation context, entities, and enabling semantic search across sessions.
      21 npm
      1
      MIT
    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

    C2.8/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Memory tools clearly separate get (by ID), search (semantic), and list (paginated) operations, while API keys, projects, config, and status tools are uniquely scoped. No two tools overlap significantly.

    Naming Consistency5/5

    All 17 tools follow a consistent verb_noun snake_case pattern, using plural nouns for list/search and singular for point operations. Verb choices are clear (create, get, update, delete, list, search, rotate, set). No mixing of conventions.

    Tool Count4/5

    At 17, the tool count is slightly above the typical 3-15 range, but the breadth of domains (memories, API keys, projects, config, status) justifies the extra tools. It feels well-scoped for a general-purpose backend server.

    Completeness3/5

    Memory management is fully covered with CRUD plus search. API key lifecycle is also solid. However, project support only includes create and list—no get, update, or delete—leaving a notable gap in the project resource lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources