Changelog
Release notes and notable changes to Memco.
September 2026
SDKs v0.2: networks and the users of your product
The Python, Node.js and Go SDKs can now build Shared Memory into a product you ship to your own customers.
Memory networks. A client authenticated as an API client creates and manages memory networks, arranged in a hierarchy: one per customer, a network per team or project under it, a parent network you maintain that every customer reads from, or a network shared across customers. Writes stay in the network they were made in; reads flow down from every network above.
The users of your product. Register your own users with Memco by your id for them, place them in a customer's network, and open sessions that act as them. The SDK issues a short-lived key for each session, renews it, and ends it when the session closes.
Client credentials. MEMCO_CLIENT_ID and MEMCO_CLIENT_SECRET authenticate your backend as an API client; the SDK exchanges them for a token and keeps it renewed.
Embedding memory in your product →
Python and Node.js SDKs (v0.1)
Official SDKs for Memco Shared Memory are now available for Python and Node.js, open source under the MIT license at github.com/memcoai/memcoai.
pip install memcoai
npm install @memco/memcoaiBoth SDKs provide every memory operation, sessions that bind every call so a session id can never be dropped, typed results and typed errors, and an agent toolset that exports the memory tools to LangChain, the Anthropic SDK, and the OpenAI SDK, described in the same words the hosted MCP server uses. Python ships sync and async clients; Node.js ships ESM and CommonJS builds with full type declarations.
For existing API users: MEMCO_API_KEY is still honored but now logs a warning; use MEMCO_API_TOKEN. If you installed a pre-release from the repository's git branch, remove that source from your dependencies so the published package is used.
Personal Memory (v0.1)
Memco Personal Memory is now available. A hosted personal memory store that works across all your MCP-compatible AI agents.
Your preferences, working style, and context carry between Claude, ChatGPT, Cursor, and any other MCP-compatible client. Every agent starts where the last one left off.
New MCP server: https://spark.memco.ai/mcp-personal
Seven tools: start_session, search, list_memories, get_memory, write_memory, update_memory, delete_memory.
Personal Memory is free, private to you, and manageable through the Memco dashboard. It works alongside Shared Memory on the same platform.
Get started with Personal Memory →
August 2026
Knowledge Work domain
Memco Shared Memory now supports a second domain: knowledge, designed for AI assistants doing general knowledge work. Claude Desktop, ChatGPT, Grok, and other MCP-compatible assistants can connect to the same Memco endpoint and use the same tools to search, contribute, and build on shared knowledge.
The knowledge work domain uses the same trust model, memory ops, and governance as the coding domain. Agents connect over MCP using the existing endpoint (https://spark.memco.ai/mcp); the domain is selected at session start.