Credentials. If the bridge points at PostgreSQL, the DSN contains database credentials, so load it from deployment configuration rather than hard-coding it.
Who it is forA platform engineer whose agent runs in another language and needs to share the Python memory runtime through a separate process.
The problemThe agent host cannot import the Python library directly, so memory is unavailable to it.
The outcomeThe host talks to the memory runtime over stdio JSON-RPC and can capture, recall, and search memory.
What you need first
- Python 3.12 or newer
- pip to install the octop-memory package
- A database path for local SQLite storage, or a PostgreSQL DSN for server deployments
- An injected LLMClient only if you want automated extraction, promotion, or page regeneration; manual storage and lexical recall work without a model
Steps
- Run
pip install octop-memory - Start the
octopmemory-bridgeentry point as a subprocess and connect to its stdio stream (inferred, check the README) - Send a JSON-RPC request from the host to capture a turn
- Send a JSON-RPC recall request with a query
- Check that the response contains the text you captured
Prompt for your agent
Use the octop-memory repo to start the octopmemory-bridge process for the host <host name> and send one capture and one recall request for the query <query>. Return the recall response. Verify that the captured text appears in the recall response.
Caveat. The README documents the bridge entry point but not its request method names, so take the exact JSON-RPC methods from the integration guide before you send requests.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for TencentCloud/octop-memory and "Expose memory to agents in other languages over JSON-RPC"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer