Skip to content
Docs menu

Tool reference · Team server (remote)

memory_save

Saves a record into one workspace, personal by default, with you recorded as the author from your token.

team server /mcp
Caution. Access is controlled only by scope. Tags starting with scope:, team: or user: are rejected. Reusing a request_id with different arguments is refused; the same arguments return the original result.

When to use

  • You want to keep a note only for yourself (the default scope).
  • A decision or convention should be visible to your whole team.
  • A client may retry after a timeout and you must not create the record twice.

Parameters

NameTypeDefaultDescription
request_id string (uuid) — —
scope { kind, team_id } — —
contentrequired string — (min length 1, max length 200,000)
type "fact" | "decision" | "solution" | "lesson" | "convention" "fact" —
project string "general" (min length 1, max length 128)
tags string[] — —
context string "" (max length 200,000)
importance "low" | "medium" | "high" | "critical" "medium" —
source_format "auto" | "conversation" "auto" —
branch string "" (max length 128)

Example

Arguments

{
  "request_id": "0b6f3c2e-8a41-4d7e-9c55-1f2a3b4c5d6e",
  "scope": {
    "kind": "team",
    "team_id": "engineering"
  },
  "content": "Use pgbouncer in transaction mode for the billing API.",
  "type": "decision",
  "project": "billing-api",
  "tags": [
    "postgres",
    "pooling"
  ],
  "importance": "high"
}

Result shape

{
  "scope": {
    "kind": "team",
    "team_id": "engineering"
  },
  "scope_tags": [
    "scope:team",
    "team:engineering"
  ],
  "data": {
    "id": 812,
    "type": "decision",
    "content": "Use pgbouncer in transaction mode for the billing API.",
    "project": "billing-api",
    "tags": "[\"postgres\", \"pooling\"]",
    "status": "active",
    "created_at": "2026-09-25T09:14:02Z",
    "created_by": {
      "user_id": "vasya",
      "display_name": "Vasya",
      "client": "codex"
    },
    "updated_by": {
      "user_id": "vasya",
      "display_name": "Vasya",
      "client": "codex"
    },
    "revision": 1,
    "saved": true,
    "deduplicated": false,
    "privacy_redacted": false
  }
}

data is the stored record plus authorship; only some columns are shown. If the quality gate rejects the content, data is { saved: false, quality }.

Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.

Server description

The description the server sends to your agent in tools/list, captured from the v14.7.0 source:

Save memory. Default scope is personal; author comes from your token.

Found a mistake? Open an issue on GitHub.

Search