Muse compatibility
STEM with Muse and Muse Code
Understand the difference between unverified Muse consumer MCP compatibility and the documented Muse Code remote MCP configuration.
Documentation reviewed . Host verification dates are listed separately.
Compatibility unverified for Muse. Muse consumer and Muse Code are different clients. A custom connector feature in one product does not establish remote MCP support in the other.
Muse consumer app
Meta documents creating custom connectors by asking Muse in chat, but the consumer documentation does not confirm a native remote Streamable HTTP and OAuth connection to STEM. We have not verified that path end to end. See Meta's Muse connector guidance.
Use this compatibility question before attempting setup:
Can this Muse client connect to a remote Streamable HTTP MCP server at https://awase.dev/stem using OAuth and dynamic client registration? If supported, guide me through browser authorization for my existing STEM account and list the tools. If unsupported, explain the missing capability and stop. Do not request passwords or private keys in chat.
If the client cannot perform that flow, use another supported client to manage your STEM memory. A tool listing and successful authorized call are required before treating Muse as connected.
Muse Code: documented setup
Muse Code separately documents remote MCP and browser OAuth. Merge this server into its settings file:
{
"mcp_servers": {
"stem": {
"transport": "streamable_http",
"url": "https://awase.dev/stem",
"enabled": true,
"mode": "optional"
}
}
}
Authenticate with:
muse mcp login stem
Sign in to your existing STEM account in the browser, then use /mcp to inspect the server and tools. Follow with the save and recall test. This is a documented configuration, not a claim of a completed STEM host test. See Meta's Muse Code MCP and OAuth instructions.
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.
← Back to the agent hub · Machine-readable tool schemas