ainative-opencode-memory-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AINATIVE_API_KEY | Yes | Required. Free at ainative.studio | |
| AINATIVE_API_URL | No | Override for self-host | https://api.ainative.studio |
| OPENCODE_MEMORY_NAMESPACE | No | Isolate memories per project | opencode |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| opencode_search_memoryA | Semantic search over everything the agent has remembered. Returns the most relevant memories for a query. |
| 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. |
| opencode_memory_statsA | Report how many memories are stored for this OpenCode namespace. |
| opencode_clear_memoryA | Delete stored memories. Optionally scope to a tag; with no tag, clears ALL memories in the namespace (destructive). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
Five tools is a well-scoped number for a memory management server, covering store, retrieve, recall, stats, and clear without unnecessary bloat.
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.