feat(mem0-plugin): support self-hosted Mem0 server via MEM0_BASE_URL

JDSS/mem0

Adds an optional MEM0_BASE_URL override (env var, falling back to
settings.json's base_url, defaulting to the hosted Platform unchanged)
so the plugin's REST-backed hooks can talk to a self-hosted server/
deployment instead of api.mem0.ai.

A new scripts/_api.py centralizes the hosted-vs-self-hosted protocol
differences (unversioned paths, X-API-Key auth, agent_id instead of
app_id) that every hook previously hardcoded, and all 9 urllib call
sites now route through it.

MCP tools have no self-hosted backend (server/ implements no MCP), so
they continue to talk to the hosted Platform regardless of
MEM0_BASE_URL; this is documented rather than silently left unclear.
Coding-category customization also has no self-hosted SDK equivalent
and now skips cleanly with a log message instead of failing.

Closes MEM-5647

This commit is contained in:

kartik-mem0

2026-08-13 18:29:24 +05:30

parent 96d45b78c7

commit 16c2cfe50e

18 changed files with 579 additions and 151 deletions

									
										integrations/mem0-plugin/scripts/load_settings.py
									
		+1
		
												View File
												
				@@ -18,6 +18,7 @@ DEFAULTS = {

				    "confidence_threshold": 0.3,

				    "global_search": False,

				    "debug": False,

				    "base_url": "",

				}