Manifests mirror the fluxcd repo's apps/apps/<name>/<name>/{app,backup} nesting
and build clean with kubectl kustomize; they are unverified against a live
cluster. README documents the build, the deploy order, MCP_TOKEN rotation across
its two Vault paths, harness wiring, and every deviation from PLAN.md.
20 lines
1.1 KiB
JSON
20 lines
1.1 KiB
JSON
{
|
|
"_howto": "Add this object to mcp.client_configs in kubernetes/apps/apps/bifrost/bifrost/app/config.json. That file is a configMapGenerator input, so editing it is the whole change — the generated ConfigMap's hash suffix moves and Flux rolls the Deployment. Commit it only AFTER mdmem itself is healthy, so a failure is attributable to one change.",
|
|
"name": "mdmem",
|
|
"connection_type": "http",
|
|
"connection_string": "http://mdmem.apps.svc.cluster.local:8080/mcp",
|
|
"auth_type": "headers",
|
|
"headers": { "Authorization": "env.MDMEM_AUTH_HEADER" },
|
|
"is_ping_available": false,
|
|
"is_code_mode_client": false,
|
|
"_comment": "Long-term agent memory. Code Mode deliberately off: memory bodies are untrusted text, and code mode hands tool output to a model that then writes executable code. Revisit only after the prompt-injection behaviour is tested with a local model. tools_to_execute is an explicit allow-list, not '*', so a future mdmem release cannot add a destructive tool that silently becomes reachable.",
|
|
"tools_to_execute": [
|
|
"memory_search",
|
|
"memory_get",
|
|
"memory_write",
|
|
"memory_update",
|
|
"memory_supersede",
|
|
"memory_flag"
|
|
]
|
|
}
|