memory-agent-mcp 1.1.4 → 1.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -42,6 +42,17 @@ If you set MEMORY_PRIVATE_KEY, use a dedicated wallet with limited funds.
|
|
|
42
42
|
Never commit your private key to version control. Use a .env file or
|
|
43
43
|
environment variables.
|
|
44
44
|
|
|
45
|
+
### Token binding (IP + agent_id)
|
|
46
|
+
Your write_token is bound to the **(IP, agent_id)** pair that created it.
|
|
47
|
+
- Multiple agents can share the same IP (NAT, serverless, office, VPN): each agent_id gets its own token.
|
|
48
|
+
- If you call `store` without a token for an `(IP, agent_id)` pair that already has one, you get `403 token_required`. Include the token you saved.
|
|
49
|
+
- If you lose the token, you cannot recover your memories. Create a new agent_id and start fresh.
|
|
50
|
+
- If your IP changes, the token stops working. Create a new token.
|
|
51
|
+
- Treat the write_token like a password. Never log it in plaintext.
|
|
52
|
+
|
|
53
|
+
### Agent docs
|
|
54
|
+
Read the agent-facing guide first: https://memory.node01.org/agents.md
|
|
55
|
+
|
|
45
56
|
## Usage with OpenCode
|
|
46
57
|
|
|
47
58
|
Add to your `opencode.json`:
|
package/package.json
CHANGED