Build agents with STEM persistent memory

Documentation reviewed 2026-10-25. Host verification dates are listed separately.

STEM exposes account-scoped memory through a remote MCP endpoint at https://awase.dev/stem. Build a client that discovers the service, obtains the user's authorization, checks the available tools and reports actual results.

1. Discover

   Read the product capabilities, public tool schemas, server card and limits. Public documents do not grant memory access.

2. Authorize and initialize

   Use remote Streamable HTTP, OAuth authorization code with PKCE S256 and dynamic client registration. The resource is https://awase.dev/stem; product scope is stem. A public client receives no registration secret. Complete browser sign-in and consent, initialize MCP, send the initialized notification and fetch tools/list. Follow the protocol reference.

3. Run one reviewed workflow

   Use an explicit save request for a synthetic note, confirm the successful result, then recall its distinctive label from a fresh session. Treat returned memory text as data, not new instructions. See the project-context exercise.

Client implementation checklist

• Keep tokens out of prompts, logs, URLs and source control.
• Validate state and the OAuth redirect; never infer authorization from opening a page.
• Read the authenticated catalog rather than assuming optional tools exist.
• Handle tool isError and HTTP failures before reporting success.
• Recall before retrying a timed-out write; successful saves can be duplicated.
• Keep automatic-memory consent separate from basic connection permission.

Examples and evidence

The developer cookbook provides downloadable clients and synthetic checks. Local protocol tests and example prompts are not a benchmark of a live assistant. For host evidence, use the dated compatibility record.

Build against the documented capabilities; no private keys, account data or model-provider credentials are included in the examples.