Connect other MCP clients to STEM

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

Documented setup. Compatibility depends on the client, its configuration and host policies. A model name by itself does not tell you whether its application supports MCP.

Connection requirements

Your client needs remote Streamable HTTP, browser OAuth with PKCE S256, and dynamic client registration. Set the server name to STEM and URL to https://awase.dev/stem. If asked, use resource https://awase.dev/stem and product scope stem. Allow the client to discover authorization metadata and complete browser sign-in with your existing STEM account.

Do not choose a local stdio-only connection for this hosted URL or require a persistent SSE stream. No account password or manually generated private key needs to be pasted into a conversation. See the MCP server reference for discovery endpoints and schemas.

VS Code / Copilot

Merge this entry into .vscode/mcp.json, preserving existing servers:

{
  "servers": {
    "stem": {
      "type": "http",
      "url": "https://awase.dev/stem"
    }
  }
}

Review and trust the server configuration, complete its OAuth prompt and enable the tools in your agent chat. Follow VS Code's MCP setup instructions for user-level configuration and organizational controls. This is documented setup, not a verified STEM host test.

Zed

In Settings → AI → MCP Servers, add a remote server, or merge this into your settings:

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

Leave out a preset Authorization header so Zed can start OAuth. Review the browser consent, then enable STEM tools in Agent. See Zed's MCP documentation. This is documented setup, not a verified STEM host test.

Other developer clients

Dedicated guides cover Cursor, Claude Code and Muse Code. For another host, use its official custom-MCP instructions and the requirements above. If the host cannot complete OAuth or discover STEM tools, do not claim compatibility from the configuration file alone.

Verify your connection

Follow the three-step save and recall check. Confirm the tool result, then recall the same test note in a fresh conversation or another connected assistant. An opened link, installed configuration or assistant saying “connected” is not proof of a completed save.

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.