Skip to main content
Glama
topoteretes

cognee-mcp

by topoteretes
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

remember

Store text or files in AI memory, choosing permanent graph storage with entity extraction or quick session caching. This makes data retrievable and queryable for later AI tasks.

Instructions

Store data in memory.

Two modes depending on whether session_id is provided:

Without session_id (permanent memory): Runs the full add + cognify pipeline to ingest data and build the knowledge graph.

With session_id (session memory): Stores the data in the session cache only. Fast, no entity extraction. Omit session_id when the content should be stored as permanent graph memory.

Pass either data (text) or filename + content_base64 (a file upload, up to 10 MB), not both. File uploads are permanent-memory only and don't support session_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe text content to store. Mutually exclusive with filename/content_base64.
filenameNoOriginal filename for a file upload. Used to derive the stored document's name. Requires content_base64.
backgroundNoQueue permanent ingestion as a background task and return immediately instead of waiting for the pipeline. Use when the caller has a request deadline shorter than ingestion takes. Ignored with session_id, which is already fast. Errors surface via cognify_status, not the return value.
session_idNoSession ID. When set, stores in session cache only.
dataset_nameNoTarget dataset name. Defaults to the current MCP client's agent-scoped dataset (e.g. "cursor_vscode_memory"), or "main_dataset" if no client identity is detected.
custom_promptNoCustom prompt for entity extraction (permanent mode only).
content_base64NoBase64-encoded file content to ingest. Requires filename.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / background
      Added value: +{
+  "default": false,
+  "description": "Queue permanent ingestion as a background task and return immediately\ninstead of waiting for the pipeline. Use when the caller has a request\ndeadline shorter than ingestion takes. Ignored with session_id, which\nis already fast. Errors surface via cognify_status, not the return\nvalue.",
+  "type": "boolean"
+}
  2. Changed15 schema fields changedv1.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / content_base64
      Added value: +{
+  "default": null,
+  "description": "Base64-encoded file content to ingest. Requires filename.",
+  "type": "string"
+}
    • addedInput schema / properties / custom_prompt / description
      Added value: +"Custom prompt for entity extraction (permanent mode only)."
    • removedInput schema / properties / custom_prompt / title
      Removed value: -"Custom Prompt"
    • addedInput schema / properties / data / default
      Added value: +null
    • addedInput schema / properties / data / description
      Added value: +"The text content to store. Mutually exclusive with\nfilename/content_base64."
    • removedInput schema / properties / data / title
      Removed value: -"Data"
    • addedInput schema / properties / dataset_name / description
      Added value: +"Target dataset name. Defaults to the current MCP client's\nagent-scoped dataset (e.g. \"cursor_vscode_memory\"), or\n\"main_dataset\" if no client identity is detected."
    • removedInput schema / properties / dataset_name / title
      Removed value: -"Dataset Name"
    • addedInput schema / properties / filename
      Added value: +{
+  "default": null,
+  "description": "Original filename for a file upload. Used to derive the stored\ndocument's name. Requires content_base64.",
+  "type": "string"
+}
    • addedInput schema / properties / session_id / description
      Added value: +"Session ID. When set, stores in session cache only."
    • removedInput schema / properties / session_id / title
      Removed value: -"Session Id"
    • removedInput schema / required
      Removed value: -[
-  "data"
-]
    • removedInput schema / title
      Removed value: -"rememberArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  3. Addedv1.4.1
  4. Removedv1.4.0
  5. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden of disclosing behavior. It explains the pipeline variants, performance characteristics, error handling (errors via cognify_status), and constraints on file uploads. This is thorough for a memory storage tool.

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

Conciseness4/5

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

Well-structured with clear sections for modes and input constraints, but slightly verbose. It could be tightened while retaining key information.

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

Completeness4/5

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

Given the tool's complexity (two modes, multiple parameters, file uploads) and the existence of an output schema, the description covers the essential nuances thoroughly. Minor omissions like return format are handled by the output schema.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents parameters. The description adds value by explaining mode interplay (e.g., background ignored with session_id) and mutual exclusivity, but many details are already in schema descriptions.

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 clearly states the tool stores data in memory and distinguishes two modes (permanent vs session memory) based on session_id. It explicitly contrasts with sibling tools like recall and forget.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use each mode, when to omit session_id, and constraints on data vs file uploads (mutually exclusive). It clarifies that file uploads are permanent-only and that background mode is for avoiding deadline issues.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/topoteretes/cognee'

If you have feedback or need assistance with the MCP directory API, please join our Discord server