---
title: Persistent memory for Vercel AI SDK agents, on your own machine
slug: semurg-memory-for-vercel-ai-sdk
date: 2026-10-25
author: Semurg
section: how-to
tags: [vercel-ai, typescript, mcp, agents, memory, how-to]
summary: Give an agent built with the Vercel AI SDK a memory that outlives the session, on your own disk, through the SDK's own MCP client, with the exact TypeScript program our tests run.
status: published
covers: [route:POST /v1/mcp, route:POST /v1/memory/recall, mcp:memory_remember, mcp:memory_recall]
constants: [24.04, 22]
---
> Last checked on r11.132.20261027.a274a28 (27 Oct 2026): every command below ran on a fresh node of that release. The current release is r11.135.20261028.2ff2348 (28 Oct 2026), and the commands have not been re-checked on it yet.

> Tested end to end with `ai 7.0.154` and `@ai-sdk/mcp 2.0.85`. The release it ran on is named in the checked line at the top of this page.

An agent built with the Vercel AI SDK forgets what it learned when its session ends. This guide gives it a memory that outlives the
session: a Semurg node on your own machine, reached through the SDK's own `createMCPClient`, where every fact stays on your disk and comes
back cited to where it was said. Any other agent or framework that uses the same node and the same scope reads the same memory.

> Diagram vercel-ai-memory: Your AI SDK program stores a fact through the SDK's MCP client over HTTP; your node keeps it in the scope you named, on your own disk; a later run, another agent or a plain HTTP call on the same scope reads it back, cited.

## What you need

- An Intel or AMD x86_64 machine with Ubuntu 24.04, on Linux directly or on Windows through WSL2. One node is free, with no licence key.
- Node.js 22 and npm. We test in the official `node:22-slim` container.

## Step one: install a node

On Ubuntu 24.04 (x86_64), with sudo:

```bash
curl -fsSL https://one.semurg.io/install | sudo bash
```

The [install page](/install) lists what the installer needs and what it changes. The installer ends by printing your API token, and the
node keeps a copy. Put it in a file only you can read, and have every new terminal load it:

```bash
mkdir -p ~/.config/semurg
(umask 077; sudo grep '^SEMURG_API_TOKEN=' /etc/semurg/semurg.env | cut -d= -f2- > ~/.config/semurg/token)
echo 'export SEMURG_API_TOKEN="$(cat ~/.config/semurg/token)"' >> ~/.bashrc
export SEMURG_API_TOKEN="$(cat ~/.config/semurg/token)"
```

## Step two: install the AI SDK and its MCP client

Make a folder for the program. It is an ES module, so the folder's `package.json` says so, as in the setup we test; the MCP client is its
own package, `@ai-sdk/mcp`, and `tsx` runs the TypeScript file directly.

```bash
mkdir ~/semurg-vercel-ai && cd ~/semurg-vercel-ai
npm init -y && npm pkg set type=module
npm install ai tsx zod @ai-sdk/mcp
```

## Step three: connect

Save the program below as `snippet.ts` in that folder. It is the program our tests run as written, shown here from the
[agents page](/agents#vercel-ai) rather than copied, so what you read is always the file that ran.

```typescript
// Run: npx tsx snippet.ts   (SEMURG_API_TOKEN must be set in the environment)
import { createMCPClient } from "@ai-sdk/mcp";

const url = process.env.SEMURG_MCP_URL ?? "http://127.0.0.1:4000/v1/mcp";
const headers = {
  Authorization: `Bearer ${process.env.SEMURG_API_TOKEN}`,
  "X-Semurg-Scope": process.env.SEMURG_MCP_SCOPE ?? "default",
};
const facts = {
  entities: [{ name: "Ada", type: "person" }, { name: "Acme", type: "organisation" }],
  relations: [{ source: "Ada", target: "Acme", type: "WORKS_AT" }],
};

async function main() {
  const client = await createMCPClient({ transport: { type: "http", url, headers } });
  try {
    const tools: Record<string, any> = await client.tools();
    const opts = { toolCallId: "1", messages: [] };
    await tools["memory_remember"].execute({ facts }, opts);
    console.log(JSON.stringify(await tools["memory_recall"].execute({ subject: "Ada" }, opts)));
  } finally {
    await client.close();
  }
}

main().catch((e) => {
  console.error(e);
  process.exit(1);
});
```

*Ran: this exact file, end to end against a fresh node on release r11.132.20261027.a274a28, with ai 7.0.154, @ai-sdk/mcp 2.0.85. Install: `npm install ai tsx zod @ai-sdk/mcp`. Its run record: https://one.semurg.io/agents#vercel-ai*

It reads your token from `SEMURG_API_TOKEN`, the node's address from `SEMURG_MCP_URL` (without it, `http://127.0.0.1:4000/v1/mcp`) and
the scope from `SEMURG_MCP_SCOPE` (without it, the scope named `default`). It creates an MCP client over the `http` transport with the
token and the `X-Semurg-Scope` header, stores two facts with `memory_remember` (Ada works at Acme), prints what `memory_recall` returns
for Ada as JSON and closes the client.

## Step four: run it

Give the program a scope of its own, so it never writes into a memory you use for real work:

```bash
export SEMURG_MCP_SCOPE=try-vercel-ai
npx tsx snippet.ts
```

It prints the recall result as JSON, which carries the node's answer for Ada: `state` set to `answered` and the `WORKS_AT` fact that
links Ada to Acme, each item cited. Storing the same facts again changes nothing, so it is safe to run twice.

Now read the same fact from outside the SDK, over plain HTTP. What one client writes, any other client on the same node and scope reads:

```bash
curl -sS http://127.0.0.1:4000/v1/memory/recall \
  -H "Authorization: Bearer $SEMURG_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"scope":"try-vercel-ai","subject":"Ada"}'
```

## The memory tools in the AI SDK

`client.tools()` returns the memory tools keyed by their own names; the program calls them with `execute`. The same tools object is what
you hand to the SDK's text generation calls, and the model then chooses (our test calls the tools directly, without a model).

- `memory_status`: reports whether shared memory is on for this node and which of your scopes hold facts.
- `memory_remember`: stores entities, the relationships between them and the passages they came from, or plain text, with an optional source label and date.
- `memory_recall`: recalls what is stored about one named entity, its own facts first, each item cited.
- `memory_relate`: adds one typed relationship between two entities in a scope, creating an end that is not stored yet.
- `memory_context`: answers a question in plain words with cited items and a verdict on whether the store covers it.
- `memory_document`: takes a whole document (PDF with a text layer, Word, HTML or plain text) and stores it as cited passages in a scope.
- `memory_forget`: deletes one thing per call: an entity and everything that names it, one fact, one document, every document under a source label, or the whole scope. It is unreachable at once and not yet wiped from the disk.
- `memory_export`: reads everything a scope holds, one page per call: send each reply's `next` back as `cursor` until it is empty. The records are the entities, the facts with their dated sources and whether each is current or ended, and each stored document once; a forgotten passage is never exported.
- `memory_import`: stores the records `memory_export` produced into any scope, through the same writes `memory_remember` makes. A page sent twice stores nothing twice, and the reply names every record it skipped.

Every answer says its `state`: `answered`, `nothing_stored` (nothing stored matched, so the agent should say it does not know) or `could_not_judge`.

## Troubleshooting

- An error that names `401` (unauthorised): `SEMURG_API_TOKEN` is not set in this shell, so the program sent no token, or it holds another node's token. Run the last line of step one.
- `Cannot find package '@ai-sdk/mcp'`: the MCP client is a separate package. Run the install line of step two in the program's folder.
- Calling a tool yourself, outside a model call, needs the options object the program passes to `execute` (a tool call id and the messages).
- An error about `import` statements: run the program from the folder made in step two, whose `package.json` sets `"type": "module"`.
- After the node restarts (an update restarts it), the first call can fail; in our October 2026 restart test, run on an earlier release, the SDK's client then reconnected by itself. For a node that is up but stalled, set the per-call timeout your framework offers.

Use `127.0.0.1` rather than `localhost`: on Ubuntu `localhost` can resolve to the IPv6 address first, and the node listens on IPv4 loopback
only. To reach a node on another machine, set `SEMURG_MCP_URL`, or forward its port with `ssh -N -L 4000:127.0.0.1:4000 you@your-node`.

## Next

- The [agents page](/agents): every framework program, with its versions and the release it last ran on in our tests.
- [Give your agent persistent memory with MCP in five minutes](/blog/agent-memory-mcp-five-minutes): the memory calls over plain HTTP too.
- [Connecting to Semurg over MCP](/blog/connect-over-mcp): the endpoint, the protocol versions it speaks and how a refusal comes back.
- If a step does not work, tell us on the [contact page](/contact), with the reply you got.

*This post was written with AI assistance. Every result in it is checked against a published release or record before the post goes out.*