Common questions
Muse does not show an authorization card
Muse configures its custom MCP client through conversation. The agent must use credentials.request_api_access to show the real OAuth consent card. It must use the endpoint's actual discovery metadata and credential store. The shared skill contains the client procedure. A missing card is a setup failure; report it rather than asking for credentials in chat.
The connection fails
Use the complete public HTTPS MCP address supplied by Nowledge Mem. Keep its query unchanged. For Nowledge Cloud, the endpoint is https://cloud.nowledge.co/mcp?space_protocol=exact-v1.
For Mem running on your computer, keep Mem and Access Anywhere running. A hosted tool cannot reach localhost or a private LAN address. If a temporary address changes, update the host connection; Nowledge Link provides a stable address. Complete pairing and OAuth in the same browser profile. Never paste an API key or token into chat.
The connection works, but conversations are not saved
The host needs the sync_thread tool and explicit threads:sync permission; readback needs threads:read. Memory writes use a separate mem:write scope. Reauthorize a read-only connection with the required permissions. Verify one narrowly scoped write and read back the stored originals in the intended Space.
The setup prompt requests the full current conversation, including each assistant reply, in the same Thread. The host can save only originals it can access. A connected status alone does not prove automatic sync. The shared skill defines verification and recovery; report unavailable tools or reply access instead of claiming success.
