Skip to main content
Glama
AINative-Studio

ainative-opencode-memory-mcp

Official
by AINative-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ainative-opencode-memory-mcp

No user-submitted related servers found.

    Related Servers

    • arcane

      Edition-X
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.
      MIT

    • AI Agent History RAG MCP

      velenzaboc
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory across AI coding agent and chat history (Claude Code, Codex, Gemini CLI, ChatGPT, and more) via retrieval-augmented generation, enabling semantic and hybrid search to retain context across sessions.
      5
      MIT

    • MCP Vector Memory

      vertexhub-ai
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI coding agents with persistent, long-term memory through local semantic search and SQLite storage. It enables agents to save and retrieve architectural decisions or project context across different conversation sessions without requiring cloud services.
      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

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools are mostly distinct: store, search, recall, stats, clear each have clear roles. Some overlap exists between search_memory and recall_context, but descriptions clarify recall_context is for session-start context loading while search_memory is for arbitrary queries.

    Naming Consistency4/5

    All tools share the 'opencode_' prefix and use snake_case, following a verb/object pattern. Minor deviation: 'memory_stats' is noun_noun instead of verb_memory, and 'recall_context' uses context instead of memory, but the naming is still predictable and readable.

    Tool Count5/5

    Five tools is a well-scoped number for a memory management server, covering store, retrieve, recall, stats, and clear without unnecessary bloat.

    Completeness4/5

    CRUD-like coverage is solid: store (create), search/recall (read), clear (delete), and stats (count). Missing an update operation, but memory overwriting is not a standard need and the surface feels complete for the domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources