Connect STEM shared memory to Claude

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

Tested workflow. An existing Claude remote connector has completed an authorized save and recall in the same chat, another connected assistant and a fresh Claude chat. Claude Code configuration below is documented setup, not a separate STEM runtime certification.

Claude remote connector

1. Open the Stem connector listing in Claude. Alternatively, open Claude's connector settings and add a custom remote connector named STEM.
2. For a custom connector, enter https://awase.dev/stem. Use browser sign-in with OAuth. If Claude asks how to identify its OAuth client, choose Register automatically, which uses STEM's dynamic client registration.
3. Sign in to the same STEM account used by your other assistants. Confirm the account, select Only save when I ask for a manual first test, approve access and complete the return to Claude. Enable the connector in a conversation and run the save and recall test.

Claude's organization controls and account limits may affect setup. Its remote connectors are account-based and differ from local desktop configuration files. Follow Claude's current custom-connector instructions for your account.

Use the same STEM account in each assistant. Your assistant may have its own subscription requirements, account restrictions and tool approvals. A connection is ready when an authenticated STEM tool succeeds.

Verify persistent memory across conversations

Start with manual saving: choose Only save when I ask during STEM consent if that choice is shown. Follow the three-step save and recall check: explicitly approve one harmless note, confirm the successful save result and memory ID, then recall that note in a fresh conversation or another connected assistant. Compare the retrieved text and ID before using it. An opened link, installed configuration or assistant saying “connected” is not proof of a completed save.

If authorization is waiting for a callback

Email verification and connection approval are separate steps. In the sign-in window opened by this client, confirm the intended STEM account, finish the displayed approval and memory choice, and follow Continue to your AI through the return to the original client. Keep the original client page or app open. Check its connection state and available tools after returning.

If the window expired, a button no longer responds or the client still reports no credentials, start a fresh authorization from that client’s connection settings and use the newest sign-in flow. Finish that fresh attempt rather than returning to an expired approval screen. Never paste passwords, email codes, bearer tokens or private keys into a conversation. Check an existing working connection before creating a duplicate.

Claude Code

In a terminal on the computer running Claude Code, add the remote HTTP server:

claude mcp add --transport http stem https://awase.dev/stem

Then run /mcp inside Claude Code, choose STEM and complete browser authorization. Enable its tools for the session and perform the quickstart check. See Claude Code's MCP documentation for configuration scopes and managed environments.

Continue a ChatGPT project in Claude

Ask ChatGPT to save the approved project summary to STEM, then ask Claude to recall that project. Both connectors must use the same STEM account. Follow the ChatGPT-to-Claude example and dated native recall observation. For the reverse direction, use the Claude-to-ChatGPT example. The context transfer guide explains selected notes and full-chat import limits.

Choose what gets remembered

Ask explicitly to save with remember. Optional automatic memory is a separate choice for each eligible OAuth connection in STEM Settings → Memory preferences. The agent must call memory_status with {} before an automatic save, require automaticSavingAllowed: true, and use remember_automatically. Host approvals still apply. Switching to manual does not erase existing memories.

STEM saves selected context supplied by a connected assistant. Connecting does not import earlier conversations, give access to other chats, or guarantee a save on every turn. Do not save passwords, tokens or secrets.