cognee-mcp

Overview Schema Source Related Servers Discussions Admin

recall

Search stored knowledge using natural language queries. Automatically routes to the best memory source, checking session cache first and falling back to the permanent knowledge graph when needed.

Instructions

Search memory with auto-routing and session awareness.

When session_id is provided without datasets or search_type, searches session cache first by keyword matching. Falls through to the permanent knowledge graph if no session results match.

Auto-routing picks the best search strategy when search_type is not specified.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Natural language query to search for.
`top_k`	No	Maximum results to return (default: 15).
`datasets`	No	Comma-separated dataset names to search within.
`session_id`	No	Session ID for session-first search.
`search_type`	No	Override auto-routing with one SearchType name. Completion types (answer written by an LLM): HYBRID_COMPLETION (the default when routing is off), GRAPH_COMPLETION, GRAPH_COMPLETION_COT, GRAPH_COMPLETION_CONTEXT_EXTENSION, GRAPH_COMPLETION_DECOMPOSITION, GRAPH_SUMMARY_COMPLETION, RAG_COMPLETION, TRIPLET_COMPLETION, TEMPORAL, AGENTIC_COMPLETION. Retrieval-only types (no LLM): CHUNKS, CHUNKS_LEXICAL, SUMMARIES, SKILLS, CODE. Other: CYPHER, NATURAL_LANGUAGE, CODING_RULES, GRAPH_REPORT, FEELING_LUCKY. An unknown name is rejected with a validation error.
`system_prompt`	No	Override the synthesis prompt for completion searches. When omitted, falls back to COGNEE_MCP_RECALL_SYSTEM_PROMPT / _FILE if configured on the server.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.6.0Sep 19, 2026

addedInput schema / properties / datasets / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / datasets / type
```
Removed value: -"string"
```

addedInput schema / properties / search_type / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / search_type / description

Previous value: -"Override auto-routing. Options: GRAPH_COMPLETION,\nGRAPH_COMPLETION_COT, RAG_COMPLETION, CHUNKS, SUMMARIES,\nTEMPORAL, FEELING_LUCKY, etc."New value: +"Override auto-routing with one SearchType name. Completion types\n(answer written by an LLM): HYBRID_COMPLETION (the default when\nrouting is off), GRAPH_COMPLETION, GRAPH_COMPLETION_COT,\nGRAPH_COMPLETION_CONTEXT_EXTENSION, GRAPH_COMPLETION_DECOMPOSITION,\nGRAPH_SUMMARY_COMPLETION, RAG_COMPLETION, TRIPLET_COMPLETION,\nTEMPORAL, AGENTIC_COMPLETION. Retrieval-only types (no LLM):\nCHUNKS, CHUNKS_LEXICAL, SUMMARIES, SKILLS, CODE. Other: CYPHER,\nNATURAL_LANGUAGE, CODING_RULES, GRAPH_REPORT, FEELING_LUCKY.\nAn unknown name is rejected with a validation error."

removedInput schema / properties / search_type / type
```
Removed value: -"string"
```

addedInput schema / properties / session_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / session_id / type
```
Removed value: -"string"
```

addedInput schema / properties / system_prompt / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / system_prompt / type
```
Removed value: -"string"
```

changedInput schema / properties / top_k / description

Previous value: -"Maximum results to return (default: 10)."New value: +"Maximum results to return (default: 15)."

Changed15 schema fields changedv1.5.0Aug 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / datasets / description

Added value: +"Comma-separated dataset names to search within."

removedInput schema / properties / datasets / title
```
Removed value: -"Datasets"
```

addedInput schema / properties / query / description

Added value: +"Natural language query to search for."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

addedInput schema / properties / search_type / description

Added value: +"Override auto-routing. Options: GRAPH_COMPLETION,\nGRAPH_COMPLETION_COT, RAG_COMPLETION, CHUNKS, SUMMARIES,\nTEMPORAL, FEELING_LUCKY, etc."

removedInput schema / properties / search_type / title
```
Removed value: -"Search Type"
```
addedInput schema / properties / session_id / description
```
Added value: +"Session ID for session-first search."
```
removedInput schema / properties / session_id / title
```
Removed value: -"Session Id"
```

addedInput schema / properties / system_prompt / description

Added value: +"Override the synthesis prompt for completion searches. When omitted,\nfalls back to COGNEE_MCP_RECALL_SYSTEM_PROMPT / _FILE if configured\non the server."

removedInput schema / properties / system_prompt / title
```
Removed value: -"System Prompt"
```

addedInput schema / properties / top_k / description

Added value: +"Maximum results to return (default: 10)."

removedInput schema / properties / top_k / title
```
Removed value: -"Top K"
```
removedInput schema / title
```
Removed value: -"recallArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

Addedv1.4.1Jul 30, 2026
Removedv1.4.0Jul 17, 2026
Changed1 schema field changedv1.0.2Jul 9, 2026
- changedInput schema / properties / top_k / default
```
Previous value: -10New value: +15
```
First observedv1.0.1Jun 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations present, the description carries the behavioral disclosure burden and does it reasonably well by explaining session-first fallback and automatic strategy selection. It does not describe result formatting or failure modes, but those are partly covered by the output schema and the search_type validation note in the schema.

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?

The description is compact, front-loaded with the core purpose, and each sentence adds behavior detail without repetition or filler. The paragraph breaks make the routing rules scannable.

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?

For a read-style search tool with a rich input schema and an output schema, the description plus schema covers invocation, routing, fallback, and override behavior. Nothing essential is missing for an agent to select and call the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already documented; the description adds value by explaining the conditional interaction between session_id, datasets, and search_type beyond the schema's field-level text. It clarifies that search_type is an override of routing and that session behavior changes when session_id is supplied alone.

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

Purpose4/5

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

The description opens with a specific verb and resource ('Search memory') and identifies the key behaviors ('auto-routing and session awareness'), so an agent can tell it is a retrieval tool. It does not explicitly distinguish recall from the sibling search_tools, keeping it one step below a fully differentiated purpose statement.

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 concrete routing conditions: when session_id is present without datasets or search_type, search the session cache first, then fall through to the knowledge graph; and auto-routing applies when search_type is omitted. It gives clear context for invoking the tool correctly, though it does not mention when to prefer it over sibling tools such as search_tools.

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

Deploy Server