All MCP Servers
Dev Tools & GitMCP Registrynpm5 toolsA · 81

ainative-opencode-memory-mcp

io.github.AINative-Studio · Updated

Persistent cross-session memory for OpenCode and MCP coding agents, powered by ZeroDB.

At a glance

ainative-opencode-memory-mcp is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y ainative-opencode-memory-mcp`, and declares no required credentials. It exposes 5 tools, including opencode_store_memory, opencode_search_memory and opencode_recall_context. It scores A (81/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

VS CodeVS Code InsidersCursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install ainative-opencode-memory-mcp in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install ainative-opencode-memory-mcp in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add ainative-opencode-memory-mcp -- npx -y ainative-opencode-memory-mcp

  2. Verify it's connected

    bash
    claude mcp list

  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. opencode_store_memory, opencode_search_memory, opencode_recall_context). It discovers them automatically.

What tools does ainative-opencode-memory-mcp expose? (5)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

What the code can do

Read from the published package source — never executed. Parsed 1 of 1 source file.

This server can read and write files, read your environment variables and read system information.

How it was published

  • No provenance attestation — there is nothing linking this published artifact to a specific source commit.
  • 1 npm maintainer — a single point of compromise · last published by ainative-studio.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 2 months ago — Actively maintained.
  • Repository created 2 months ago — Very new project with little track record yet.
  • 0 GitHub stars — Very little community usage so far.
  • 36 weekly downloads — Very few installs — you would be an early user.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 81

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%92%

    Last commit 87 days ago.

  • Adoption20%18%

    0 stars, 36 weekly downloads.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%100%

    Package and registry entry point at the same repository.

  • Packaging15%100%

    Publishes a pinned version (0.1.2).

Documentation

Full README

ainative-opencode-memory-mcp

Persistent memory for [OpenCode](https://opencode.ai) 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

Install

bash
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):
json
{
  "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.

Maintain ainative-opencode-memory-mcp? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![ainative-opencode-memory-mcp on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-ainative-studio-ainative-opencode-memory-mcp)](https://mcp-skills-hub.vercel.app/mcps/io-github-ainative-studio-ainative-opencode-memory-mcp)

Catalog data refreshed . Something wrong? Report it.