STEM

Grok integration

STEM with Grok chat and Grok Bot

Configure a STEM custom MCP connector in Grok chat and check Grok Bot compatibility separately before claiming a connection.

Documentation reviewed . Host verification dates are listed separately.

Documented setup for Grok chat. Grok documents custom MCP connectors. STEM has not verified this host workflow end to end. Grok Bot is a separate product and its STEM compatibility remains unverified.

Grok chat

  1. Open Grok connectors, choose New Connector, then Custom.
  2. Enter https://awase.dev/stem. Complete the OAuth sign-in with your existing STEM account and approve the requested access.
  3. Enable the connector in a conversation and run the save and recall test. Verify the tool result before reporting that the connection works.

Business or Enterprise accounts may need an administrator to provision the connector. The setup path comes from Grok's official connector documentation; account and organization policies can affect availability.

Grok Bot

Grok Bot's controls and available integrations are separate from Grok chat. Do not assume that installing a connector in Grok chat installs it in Grok Bot. Start from the provider's Grok Bot instructions and ask whether your Bot supports the required connection:

Can this Grok Bot connect to STEM at https://awase.dev/stem as a remote Streamable HTTP MCP server using OAuth and dynamic client registration? If yes, show the browser authorization step for my existing STEM account and list the available tools. If not, explain the limitation and stop. Do not ask for passwords or private keys in chat.

This question checks compatibility; it does not install anything by itself. Only treat the Bot as connected after OAuth completes and a STEM tool succeeds. If custom MCP is unavailable, use a supported client instead.

Use the same STEM account in each assistant. Your assistant may have its own subscription requirements, account restrictions and tool approvals. A connection is ready when an authenticated STEM tool succeeds.

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.