Connect STEM persistent memory to Cursor

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

Documented setup. Cursor documents remote Streamable HTTP, OAuth and dynamic client registration. This guide is based on that interface; a successful STEM save and recall in your environment is the connection check.

Observed native recall — October 25, 2026

Cursor Agents on This Mac, in a fresh conversation without a repository and with visible model label Grok 4.7 High Fast, completed OAuth-authorized recall of an isolated synthetic note that ChatGPT reported saving and Claude independently recalled. The native Cursor request supplied only the lookup label with limit 1; the response matched the reported ID and expected text. This exercised the User MCP configuration. The installed plugin runtime and saving through Cursor were not tested. See the dated three-host observation and its evidence limits.

User MCP configuration and the plugin are separate setup paths

The native recall observation above used a User MCP server. The STEM Cursor plugin source and installation instructions provide a separate packaging path; that plugin’s runtime was not exercised in the observation. Check for an existing STEM server before adding another configuration.

Add STEM to Cursor

Add STEM to Cursor →

This link prefills only the remote MCP server configuration. Review https://awase.dev/stem in Cursor, then complete OAuth with your intended STEM account. It does not install the project-context skill, create an account or prove a successful tool call. If STEM is already configured, use the existing connection. Cursor’s install-link documentation.

Manual configuration

Merge this entry into your Cursor MCP configuration. Use .cursor/mcp.json for a project or ~/.cursor/mcp.json for your user configuration; preserve any existing server entries.

{
  "mcpServers": {
    "stem": {
      "url": "https://awase.dev/stem"
    }
  }
}

1. Open Cursor's MCP settings and review the STEM server configuration.
2. Use the OAuth sign-in action. Confirm and authorize the same STEM account used by your other assistants, choose Only save when I ask for a manual first test, and finish the browser return to Cursor. The client can register automatically; no manually pasted account key is needed.
3. Enable STEM tools for Cursor Agent and run the save and recall test.

Configuration locations and OAuth behavior are described in Cursor's MCP documentation. Your organization's server and tool policies still apply.

Useful coding context to share

Save a reviewed architectural decision, deployment constraint or next-step summary. Include the project name and the relevant date or version. Another assistant can recall that context without being given your entire repository. Saving context does not itself upload source files or grant repository access.

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.

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.