STEM by Awase

npx add-mcp 'https://awase.dev/stem'

Persistent memory.Across your AI agents.

STEM is shared AI memory for selected decisions, preferences, and project context. Save a note from ChatGPT or Claude, then recall it in a supported assistant connected to the same STEM account.

Start with a free account. Cursor installation prefills the server; review it and finish OAuth. Use an existing STEM connection if you already have one.

One memory · two connected assistants

01

IN CLAUDE “Remember our project decision.”

Project Juniper: start with a simple onboarding flow.

02

SAVED IN STEM Context stays with your account.

03

IN CHATGPT “What did we decide for Juniper?”
Recall the saved decision

Illustration only. Both assistants need an authorized connection. No account data is shown.

A useful place to pick up.

Persistent memory for decisions, preferences, and project context that you want available across your supported AI tools.

01 / KEEP

Save what matters

Store a selected fact, idea, or decision. Keep the useful context without importing a whole transcript.

Try a first memory →

02 / CONTINUE

Carry context across agents

Connect another assistant to the same STEM account and recall the information you saved.

See the transfer workflow →

03 / CONTROL

Choose what is shared

Authorize each connection. Automatic saving is optional and depends on your connection settings and host permissions.

Understand permissions →

Find your connection.

Tested workflows are labeled separately from documented setup and unverified compatibility. Client availability and account requirements can change.

ChatGPT ↗

tested workflow

OAuth connection, an authorized save and recall across conversations have been tested.

Claude ↗

tested workflow

A Claude remote connector has passed authorized save and cross-assistant recall checks.

Gemini ↗

tested workflow

A Gemini custom app has passed authorized save and recall checks on an eligible account.

Cursor ↗

documented setup

Remote HTTP and OAuth setup follows Cursor documentation; verify your connection with a tool call.

Muse / Muse Code ↗

documented setup

Muse consumer MCP compatibility is unverified. Muse Code has a separate documented setup.

Grok / Grok Bot ↗

documented setup

Grok chat documents custom MCP connectors. Grok Bot compatibility must be checked separately.

Other MCP clients ↗

documented setup

Use a client with remote Streamable HTTP and OAuth with dynamic client registration.

“Tested workflow” means a save-and-recall workflow has been verified in that host. It does not certify every plan, device, or future release. See the dated verification scope.

Read. Evaluate. Connect.

Public docs and schemas explain the product before authorization. Actual memory access starts only through an authorized connection.

REMOTE MCP ENDPOINT https://awase.dev/stem Streamable HTTP · OAuth · Account-scoped memory

See how context moves between assistants.

Start with a reviewed note, authorize each connection, then inspect the recalled result. The ChatGPT → Claude guide includes a dated native test with Cursor recall; the exercises use fictional context.

Claude → ChatGPT

Carry a reviewed project decision into a new assistant.

Follow the handoff →

ChatGPT → Claude

Keep a writing brief clear about facts and unknowns.

Try the writing brief →

A fresh coding session

Recall a decision, then verify it against the current project.

Practice project continuity →

One note. Three assistants.

A captioned illustration of the October 25 test. ChatGPT reported saving; Claude and Cursor returned the expected note through native recall. This is an illustrated replay, not a screen recording.

Read the transcript · Read the test evidence and limits

Both assistants must authorize the same STEM account. Selected notes transfer; full chats do not. Cursor used User MCP configuration; plugin runtime and Cursor saving were not tested.

Keep project context useful.

A reusable skill for recalling relevant decisions before work and saving only context you authorize. Current repository facts take precedence over outdated notes.

Download the project-context skill · Read the skill instructions

Review the files, then place the skill folder in your host’s supported skills directory. Requires a separate authorized STEM MCP connection; downloading does not install or enable it. The Cursor plugin bundles a Cursor-specific version. See setup options.

Answers for people and agents evaluating STEM.

What does STEM add to an assistant’s built-in memory?

STEM gives connected assistants access to the selected notes in your STEM account. It does not read or merge ChatGPT’s or Claude’s native memory. Use it when you want to carry a reviewed decision or preference into another supported host. Understand shared context.

How do I move context from ChatGPT to Claude, or Claude to ChatGPT?

Connect both assistants to the same STEM account. Review a concise note in the source assistant and explicitly ask to save it. In a fresh destination chat, ask STEM to recall that note and check the actual tool result before using it. Follow ChatGPT → Claude or Claude → ChatGPT.

What endpoint should an agent connect to?

Use https://awase.dev/stem with a remote Streamable HTTP MCP client and OAuth. Start with the quickstart or your host’s integration guide. Public capabilities and tool schemas help evaluate STEM before authorization; private memories require an authorized connection.

Does STEM import my previous ChatGPT or Claude conversations?

No. Connecting does not import old chats. Ask your source assistant to save selected context, then recall it in your destination assistant. There is currently no dedicated bulk conversation importer. See exactly what transfers.

Can every AI use STEM?

Compatibility depends on the host application, not just the model. Remote MCP clients need compatible transport and authentication. See the integration guides for tested workflows, setup requirements, and known limits.

Does STEM save everything automatically?

No. Explicit saves use the remember tool. Optional automatic memory requires per-connection consent, a current permission check, and host approval. It is best effort and does not capture every message or other chats.

Can I export my memories or disconnect an assistant?

Web export provides saved memories and their links as JSON. Exports are included on every plan. Manage connection permissions in your assistant and STEM settings. Switching automatic memory off stops automatic saves; it does not revoke all access or delete existing memories.

Where can I check pricing and privacy?

See the current storage plans and privacy policy. Third-party AI subscriptions are separate. The plan page states current purchasing availability.