Skip to main content
Glama
Sign In
ainative-opencode-memory-mcp

ainative-opencode-memory-mcp

Official
by AINative-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ainative-opencode-memory-mcp

Persistent memory for OpenCode agents. OpenCode is stateless — it forgets everything between sessions. This MCP server gives your OpenCode coding agent long-term memory powered by AINative ZeroDB: store a codebase's decisions, conventions, and gotchas once, and recall them in every future session.

Why

OpenCode restarts with a blank slate every time. Your agent re-learns your architecture, re-asks the same questions, re-makes the same mistakes. With this MCP, it remembers:

  • Architecture & design decisions

  • Naming conventions and code style

  • Gotchas, workarounds, and "don't touch X" rules

  • User/team preferences

Related MCP server: arcane

Install

npm install -g ainative-opencode-memory-mcp

Setup (OpenCode)

  1. Get a free API key → ainative.studio/signup (Hobbyist $5/mo, 7-day free trial).

  2. Add to your OpenCode MCP config (opencode.json / MCP settings):

{
  "mcpServers": {
    "ainative-memory": {
      "command": "npx",
      "args": ["-y", "ainative-opencode-memory-mcp"],
      "env": { "AINATIVE_API_KEY": "your-key-here" }
    }
  }
}

Tools

Tool

What it does

opencode_store_memory

Remember a fact/decision/snippet (optional tags)

opencode_search_memory

Semantic search over everything remembered

opencode_recall_context

Reload relevant memories at the start of a task

opencode_memory_stats

How many memories are stored

opencode_clear_memory

Wipe memories (optionally by tag)

Example

At the start of a session, have your agent call opencode_recall_context with the file/task you're working on — it reloads what it knew. As you work, opencode_store_memory captures new decisions. Next session, it all comes back.

Environment

Var

Default

Notes

AINATIVE_API_KEY

—

Required. Free at ainative.studio

OPENCODE_MEMORY_NAMESPACE

opencode

Isolate memories per project

AINATIVE_API_URL

https://api.ainative.studio

Override for self-host

Built by AINative Studio — the AI-native dev platform with 65+ models, one OpenAI-compatible endpoint, and persistent agent memory. MIT licensed.

Available Tools

5 tools
opencode_clear_memoryA

Delete stored memories. Optionally scope to a tag; with no tag, clears ALL memories in the namespace (destructive).

Inputs: tag.

opencode_memory_statsA

Report how many memories are stored for this OpenCode namespace.

Inputs: no named parameters.

opencode_recall_contextA

Pull the most relevant remembered context for the current coding task — call this at the START of a session to reload what the agent knew.

Inputs: task (required), limit.

opencode_search_memoryA

Semantic search over everything the agent has remembered. Returns the most relevant memories for a query.

Inputs: query (required), limit.

opencode_store_memoryA

Store a fact, decision, convention, or code snippet so your OpenCode agent remembers it in future sessions. Use for things like architecture decisions, naming conventions, gotchas, or user preferences.

Inputs: content (required), tags.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • arcane

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

    • gemdex-mcp

      nikships
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding agents with a persistent memory layer to save, recall, update, and track memories across sessions and repositories using hybrid semantic search.
      5
      MIT