STEM — Persistent AI Memory

dev.awasePublished by awase.devOfficial publisherv1.0.0Updated Oct 26, 2026

Persistent memory and shared context across compatible AI assistants, with account-scoped OAuth.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that gives compatible AI assistants persistent memory and shared context, scoped to a user account via OAuth.

What you can do
  • Store and recall persistent memory across sessions for a connected assistant.
  • Share context between compatible AI assistants tied to the same account.
  • Scope stored memory to the signed-in account through OAuth.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Worth adding when you want an assistant to remember information between conversations, or to carry context across several compatible assistants rather than repeating yourself each time.
Requirements
A remote MCP endpoint at awase.dev reached over streamable HTTP; no local package or runtime is needed. An account with OAuth sign-in is required. Network access to the endpoint is needed.
Before you install
Memory is tied to your account and persists across sessions, so anything stored may be recalled later by any compatible assistant you connect. Review what gets saved and how the provider retains it before use; no tool list is published, so the exact read and write behavior is not documented here.

Installation

In SourceWeft

  1. Open STEM — Persistent AI Memory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.awase%2Fstem/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "stem-persistent-ai-memory": {
      "type": "http",
      "url": "https://awase.dev/stem"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.