Skip to content
Docs menu

Tool reference · Team server (remote)

memory_history

Lists the change events for a record and all earlier versions it replaced, oldest first, with author, time, reason and before/after state.

team server /mcp

When to use

  • You want to know who changed a team decision, when and why.
  • You need the previous text of a record that was updated.
  • A write timed out and you want to see whether it actually happened before retrying.

Parameters

NameTypeDefaultDescription
scope { kind, team_id } — —
idrequired integer — —
after integer 0 (min 0)
limit integer 50 (min 1, max 50)

Example

Arguments

{
  "scope": {
    "kind": "team",
    "team_id": "engineering"
  },
  "id": 815,
  "after": 0,
  "limit": 50
}

Result shape

{
  "scope": {
    "kind": "team",
    "team_id": "engineering"
  },
  "scope_tags": [
    "scope:team",
    "team:engineering"
  ],
  "data": [
    {
      "sequence": 31,
      "record_id": 812,
      "at": "2026-09-25T09:14:02.118Z",
      "operation": "insert",
      "actor": {
        "user_id": "vasya",
        "display_name": "Vasya",
        "client": "codex"
      },
      "reason": "",
      "revision": 1,
      "before_state": null,
      "after_state": {
        "id": 812,
        "type": "decision",
        "content": "Use pgbouncer in transaction mode for the billing API.",
        "project": "billing-api",
        "tags": "[\"postgres\", \"pooling\"]",
        "status": "active",
        "superseded_by": null
      }
    },
    {
      "sequence": 40,
      "record_id": 812,
      "at": "2026-09-25T11:02:47.503Z",
      "operation": "update",
      "actor": {
        "user_id": "petya",
        "display_name": "Petya",
        "client": "claude-code"
      },
      "reason": "Migrations need session-level advisory locks",
      "revision": 2,
      "before_state": {
        "id": 812,
        "status": "active",
        "superseded_by": null
      },
      "after_state": {
        "id": 812,
        "status": "superseded",
        "superseded_by": 815
      }
    }
  ]
}

Shortened. To get the next page, pass the last sequence you received as after. operation is insert, update, delete or confirm (a repeat save of the same content).

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:

Page through this record and its predecessors; after is the last sequence.

Found a mistake? Open an issue on GitHub.

Search