ainative-opencode-memory-mcp
Provides persistent memory for OpenCode coding agents, allowing them to store and recall architecture decisions, conventions, and gotchas across sessions via semantic search.
README
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
Install
npm install -g ainative-opencode-memory-mcp
Setup (OpenCode)
- Get a free API key → ainative.studio/signup (Hobbyist $5/mo, 7-day free trial).
- 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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.