### Install and Setup @xmemo/client CLI Source: https://xmemo.dev/product/docs Install the public CLI globally to discover the hosted service and generate an MCP profile. Copy the client-safe configuration into your local tools. ```bash npm install -g @xmemo/client npx @xmemo/client setup --url https://xmemo.dev ``` -------------------------------- ### Fetch Autonomous Agent Configuration Source: https://xmemo.dev/product/docs Use this GET request to fetch the configuration for autonomous agents. It supports OAuth-first authentication and falls back to XMEMO_KEY for headless runners. ```http GET https://xmemo.dev/api/v1/mcp/config/autonomous-agent # Preferred: auth_modes.oauth.mcpServers.XMemo # Fallback: auth_modes.xmemo_key.mcpServers.XMemo # Fixed agent id: autonomous-agent # Runner-generated instance id: XMEMO_AGENT_INSTANCE_ID ``` -------------------------------- ### Configure OAuth Client for XMemo Source: https://xmemo.dev/product/docs Use this configuration for clients supporting OAuth, such as ChatGPT or VS Code. Ensure you approve the necessary memory scopes and do not paste the XMEMO_KEY into client configurations. ```text MCP URL: https://xmemo.dev/mcp Scopes: memory:read memory:write ``` -------------------------------- ### Access XMemo Account Entry Source: https://xmemo.dev/product/docs Use the account entry point to review saved memories, check agent attribution, and find delete/export or support paths after your initial connection. ```text Account entry: https://xmemo.dev/login ``` -------------------------------- ### VS Code/GitHub Copilot MCP Configuration Source: https://xmemo.dev/product/docs This configuration is for VS Code/GitHub Copilot. It requires only the hosted server URL in mcp.json. The first tool call will initiate the browser OAuth flow. ```json { "servers": { "XMemo": { "type": "http", "url": "https://xmemo.dev/mcp" } } } ``` -------------------------------- ### Direct MCP Connection with XMEMO_KEY Source: https://xmemo.dev/product/docs This path is for clients or headless runners that cannot use OAuth. Store the XMEMO_KEY in your environment or secret store and keep the MCP URL in your configuration. Never expose the token in public documentation or chat. ```text MCP URL: https://xmemo.dev/mcp Token source: XMEMO_KEY environment variable Optional identity: XMEMO_AGENT_INSTANCE_ID ``` -------------------------------- ### Use SDK Workflow Helpers (TypeScript) Source: https://xmemo.dev/product/docs These TypeScript SDK functions help manage workflow events. They route events through capture policy before writing to memory. Ensure the client is initialized before use. ```typescript await client.taskStart('Implement MCP token repair', { source: 'codex' }); ``` ```typescript await client.recordDecision('Remote agents should use network MCP', { source: 'codex' }); ``` ```typescript await client.recordBugFix('Fixed streamable-http token identity fallback', { source: 'codex' }); ``` ```typescript await client.taskEnd('MCP token repair deployed', { source: 'codex' }); ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.