Koskamo

STEM MCP

A remote MCP server providing persistent, account-scoped memory for AI agents. It allows users to save selected context, retrieve relevant memories, link records, and delete memories across compatible AI assistants like ChatGPT, Claude, and Cursor via Streamable HTTP and OAuth.

Visit Awase LLC

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

STEM MCP logo, by Awase LLCVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Awase LLC
You need:Create a free STEM account or sign in with your email code.Use a client with remote Streamable HTTP and OAuth with dynamic client registration.Third-party AI subscriptions are separate.
MCP endpoint (Streamable HTTP)
https://awase.dev/stem
Vendor documentation

What you can do with it

  • Save selected project decisions or notes to persistent memory
  • Recall relevant context across different AI assistants
  • Link related memory records to build a knowledge graph
  • Delete specific memories to manage account data

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: dev.awase/stem@1.0.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
240 ms
95th percentile latency
240 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 240 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http stem-mcp https://awase.dev/stem

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add stem-mcp --url https://awase.dev/stem

Cursor

Merge this server into .cursor/mcp.json in your project, then enable stem-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "stem-mcp": {
      "url": "https://awase.dev/stem"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "stem-mcp": {
      "type": "streamableHttp",
      "url": "https://awase.dev/stem",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start stem-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "stem-mcp": {
      "type": "http",
      "url": "https://awase.dev/stem"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http stem-mcp https://awase.dev/stem

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "stem-mcp": {
      "url": "https://awase.dev/stem"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "stem-mcp": {
      "serverUrl": "https://awase.dev/stem"
    }
  }
}

Let your agent find its tools

Find servers like STEM MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,579

Do you run STEM MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing