mem0-mcp

add_memory

Store a new memory to persist important context. Provide user_id, agent_id, or run_id to scope it; otherwise defaults apply.

Instructions

Store a new memory. Provide at least one of user_id, agent_id, or run_id to scope it; if none are given, falls back to MEM0_DEFAULT_USER_ID. Tagged with MEM0_DEFAULT_AGENT_ID unless agent_id is given explicitly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "add_memory"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes
`run_id`	No
`user_id`	No
`agent_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the transparency burden. It discloses fallback to MEM0_DEFAULT_USER_ID and tagging with MEM0_DEFAULT_AGENT_ID unless overridden, providing useful behavioral details beyond what the schema shows. It doesn't mention permissions or side effects, but for a create operation this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, the first a clear one-line summary, followed by two purpose-specific sentences on scoping and defaults. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a simple creation operation with an output schema. The description covers all behavioral nuances (default IDs, scoping), making it complete for an agent to decide when and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does: it explains that user_id, agent_id, and run_id are for scoping, and that agent_id defaults to MEM0_DEFAULT_AGENT_ID. This gives semantic meaning to all optional parameters, though text is self-evident.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Store a new memory,' a specific verb+resource pairing that clearly distinguishes it from sibling tools like update_memory or delete_memory. It also hints at scoping semantics, reinforcing the 'add' operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear operational context: it explains the scoping requirements ('Provide at least one of user_id, agent_id, or run_id') and default behaviors. It doesn't compare to list/get/update/delete, so it lacks explicit when-not-to-use guidance, but the usage context is solid.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server