Skip to content
MMW Docs

Core memory actions use an authorized connection to https://mcp.mmwhub.tech/mcp. Transport is Streamable HTTP; API keys travel in the Bearer header, and supported web clients use OAuth.

ToolPurpose
rememberSave a note with source_id and optional fact_key/derived_from
searchRetrieve authorized records from a workspace, limit1–50
forgetSoft-delete by memory_id or source_id
validate_memoryCompare a saved source with supplied current_source_hash
search_historySearch supported session history already uploaded with consent
mmw_sync_statusLocal mmw-agent tool, unavailable through direct MCP
spool_statusLocal agent delivery queue; queued is not yet delivered

gateway_call and external integration tools cannot execute in Core. An ordinary client may retain a visible schema; the catalog profile hides these tools. Inspect the actual tools/list for your connection rather than relying on a screenshot.

The compact profile also supports preview_search and read_memory: bounded previews followed by ID/revision reads. Do not change a catalog connection merely to expose these. Ordinary setup needs only search.

search: query, workspace(default), optional scope filter, limit, current_source_hash, exclude_stale. remember: content, workspace, scope, source, source_id, source_hash, source_revision, fact_key, confidence, derived_from. Authorization selects the tenant and project; passing another tenant or project is not an access mechanism. Scope labels do not replace organization ACLs.

A new note is unverified. A matching hash or quotation alone does not verify a current fact. An upload date is not a validity date.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search","arguments":{"query":"MMWFIRSTCHECK7429","workspace":"default","limit":5}}}

The connected client adds its own authorization. Individual reference pages describe tool parameters. Quickstart · Direct Codex MCP