Skip to main content
Glama
xz0831

openclaw-brain

by xz0831
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openclaw-brain

No user-submitted related servers found.

    Related Servers

    • Neo4j GraphRAG MCP Server

      neo4j-field
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables LLMs to perform semantic and fulltext searches within Neo4j while executing complex, search-augmented Cypher queries for GraphRAG applications. It provides tools for database schema discovery and supports multi-provider embeddings to facilitate advanced graph traversals.
      5
      3
      MIT

    • RAG Memory MCP

      ttommyth
      A
      license
      Not graded
      quality
      C
      maintenance
      An advanced MCP server providing RAG-enabled memory through a knowledge graph with vector search capabilities, enabling intelligent information storage, semantic retrieval, and document processing.
      14 npm
      47
      MIT

    • GrACE-MCP

      FNZ1961
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A knowledge graph MCP server that integrates Graphiti and the ACE framework for conversational management of Neo4j-based entities and relationships. It enables AI agents to perform semantic searches, manage data isolation, and utilize automatic learning strategies.
      2
      -
    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

    A3.9/5.0

    Scored across 35 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: knowledge graph operations, memory management, session handling, pipeline config, and executable substrate tools are cleanly separated. Even similar tools like ingest_pdf and analyze_circuit_image are explicitly differentiated by workflow, and record_* tools each target a unique entity type.

    Naming Consistency4/5

    The vast majority of tools follow a clear verb_noun snake_case pattern (e.g., query_knowledge, record_hypothesis, update_stage_model). A few outliers like 'startup', 'shutdown', and 'why' break the pattern, but they are short, memorable, and do not create confusion.

    Tool Count2/5

    At 35 tools, the server exceeds the range where tool count is considered appropriate, even for a broad knowledge-management system. Many functions (e.g., model catalog management) are split into five separate tools, which could likely be consolidated without loss of clarity.

    Completeness4/5

    The domain is well covered: knowledge graph CRUD, memory management, session tracking, hypothesis/decision/bench-result lifecycle, executable-circuit query/projection/retraction, and pipeline configuration are all present. Minor gaps exist (e.g., no direct memory update/delete tool), but they are easy to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources