메뉴
Full Memory CLI command reference with all subcommands and flags. Use when you need exact command syntax, flag names, or usage examples for any `memory` CLI command.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage Emergent runtime agents and agent definitions — create, trigger, monitor runs, respond to questions, and manage agent configurations. Use when the user wants to run, inspect, or configure AI agents in an Emergent project.
Apply and export Emergent Blueprints — declarative directories of template packs, agent definitions, and seed data applied with `memory blueprints`. Use when setting up a project from a blueprint, seeding graph data, or exporting an existing project's graph as re-applyable seed files.
Manage MCP (Model Context Protocol) servers in an Emergent project — register, inspect, sync tools, and delete servers. Use when the user wants to add, configure, or troubleshoot MCP servers connected to their Emergent project.
Onboard a project into Memory — understand what the project is, choose or create a Memory project, design and install a schema (template pack), then guide on creating objects and relationships. Use when setting up Memory for a new project or codebase for the first time.
Manage LLM provider credentials and browse available models in Emergent. Use when the user wants to configure API keys, set up Vertex AI, check which models are available, or review LLM usage and costs.
Query an Emergent project knowledge base using natural language or direct hybrid search. Use when the user wants to search, explore, or ask questions about content in an Emergent project.
| name | memory-cli-reference |
| description | Full Memory CLI command reference with all subcommands and flags. Use when you need exact command syntax, flag names, or usage examples for any `memory` CLI command. |
| metadata | {"author":"emergent","version":"1.0"} |
This skill contains the complete memory CLI command reference, auto-generated from the binary.
Use this when you need to look up:
memory agents get-run, memory provider configure-project)Full command reference auto-generated from memory --help. Each section covers one command or subcommand with its synopsis, usage, and flags.
CLI tool for Memory platform
Command-line interface for the Memory knowledge base platform.
Manage projects, documents, graph objects, AI agents, and MCP integrations.
For self-hosted deployments, use 'memory server' to install and manage your server.
--compact use compact output layout
--config string config file (default is $HOME/.memory/config.yaml)
--debug enable debug logging
-h, --help help for memory
--no-color disable colored output
--output string output format (table, json, yaml, csv) (default "table")
--project string project ID (overrides config and environment)
--project-token string project token (overrides config and environment)
--server string Memory server URL
Manage and inspect ADK sessions
Manage and inspect Google ADK (Agent Development Kit) sessions.
ADK sessions represent individual agent conversation threads, including the full event history of messages and tool calls. Use the list subcommand to browse sessions for a project, and the get subcommand to inspect a specific session in detail.
-h, --help help for adk-sessions
--project string Project name or ID
Get details and event history for a specific ADK session
Get full details and the complete event history for a specific ADK session.
Outputs the entire session record as indented JSON, including all events (user messages, agent responses, and tool calls) in the session history.
memory adk-sessions get [id] [flags]
-h, --help help for get
List ADK sessions for the active project
List all ADK sessions for the active (or specified) project.
Each session is printed on one line with its session ID, App name, User ID, and last Updated timestamp in the format: ID: | App: | User: | Updated:
memory adk-sessions list [flags]
-h, --help help for list
Manage agent definitions
Commands for managing agent definitions (system prompts, tools, model config, flow type, visibility)
-h, --help help for agent-definitions
Create a new agent definition
Create a new agent definition.
Examples: memory agent-definitions create --name "my-def" --system-prompt "You are a helpful agent" memory defs create --name "extractor" --flow-type single --tools "search,graph_query" --visibility project
memory agent-definitions create [flags]
--default-timeout int Default timeout in seconds
--description string Description
--flow-type string Flow type (single, multi, coordinator)
-h, --help help for create
--is-default string Set as default definition (true/false)
--max-steps int Maximum steps per run
--model string Model name (e.g., gemini-2.0-flash)
--name string Definition name (required)
--system-prompt string System prompt
--tools string Comma-separated tool names
--visibility string Visibility (external, project, internal)
Delete an agent definition
Delete an agent definition by ID
memory agent-definitions delete [id] [flags]
-h, --help help for delete
Get agent definition details
Get full details for a specific agent definition by ID.
Prints Name, ID, ProjectID, FlowType, Visibility, IsDefault, Description (if set), System Prompt (truncated to 200 characters), Model configuration (Name, Temperature, MaxTokens), Tools list, MaxSteps, DefaultTimeout, ACP Config (DisplayName, Description, Capabilities), CreatedAt and UpdatedAt timestamps, and any extra Config JSON.
memory agent-definitions get [id] [flags]
-h, --help help for get
List all agent definitions
List all agent definitions for the current project.
Prints a numbered list with each definition's Name, ID, FlowType, Visibility, IsDefault flag, Tool count, and Description (if set).
memory agent-definitions list [flags]
-h, --help help for list
View or set per-project agent overrides
View or set per-project configuration overrides for an agent definition.
Without flags, shows the current override for the agent. With flags, sets or updates the override. Overrides are merged on top of canonical defaults each time the agent runs — non-overridden fields always get the latest code defaults.
Examples: memory defs override graph-query-agent # view current override memory defs override graph-query-agent --model gemini-2.5-pro # override model memory defs override cli-assistant-agent --max-steps 30 # override max steps memory defs override graph-query-agent --model gemini-2.5-pro --temperature 0.2 --max-steps 20 memory defs override graph-query-agent --system-prompt-file prompt.txt memory defs override graph-query-agent --sandbox-enabled false # disable sandbox memory defs override graph-query-agent --clear # remove override
memory agent-definitions override [agentName] [flags]
--clear Remove override — revert to canonical defaults
-h, --help help for override
--max-steps int Override max steps
--model string Override model name (e.g., gemini-2.5-pro)
--sandbox-enabled string Override sandbox enabled state (true/false)
--system-prompt string Override system prompt
--system-prompt-file string Read system prompt from file
--temperature float32 Override temperature (0.0-2.0) (default -1)
--tools string Override tools (comma-separated)
List all agent overrides for the project
List all per-project agent configuration overrides.
memory agent-definitions overrides [flags]
-h, --help help for overrides
Update an agent definition
Update an existing agent definition (partial update)
memory agent-definitions update [id] [flags]
--default-timeout int New default timeout
--description string New description
--flow-type string New flow type
-h, --help help for update
--is-default string Set as default (true/false)
--max-steps int New max steps
--model string New model name
--name string New name
--system-prompt string New system prompt
--tools string New comma-separated tool names
--visibility string New visibility
Manage runtime agents
Commands for managing runtime agents (scheduling, triggers, execution state)
-h, --help help for agents
--project string Project name or ID (auto-detected from config/env if not specified)
Manage built-in tools
Commands for managing built-in (Go-native) tools in the Memory platform.
Built-in tools are implemented directly in the server and are available to all agents without requiring an external MCP server connection. Examples include query_entities, brave_web_search, webfetch, and create_document.
Use 'memory agents mcp-servers' to manage externally-connected MCP servers.
-h, --help help for builtin-tools
Set runtime config for a built-in tool
Set runtime configuration key/value pairs for a named built-in tool.
Looks up the tool by name and patches its config. Only the provided keys are updated; existing keys not mentioned are left unchanged.
Examples: memory agents builtin-tools configure brave_web_search api_key=YOUR_KEY memory agents builtin-tools configure reddit_search client_id=ID client_secret=SECRET
memory agents builtin-tools configure [tool-name] [key=value ...] [flags]
-h, --help help for configure
List all built-in tools
List all built-in tools registered for the current project.
Prints each tool's enabled/disabled state, name, and description. Tools that require runtime configuration (e.g. API keys) are shown with their config status. The 'Source' column shows where the effective settings come from: project, org, or global (server default).
memory agents builtin-tools list [flags]
-h, --help help for list
Enable or disable a built-in tool
Enable or disable a built-in tool for the current project.
The tool-id is the UUID shown in 'memory agents builtin-tools list'.
Examples: memory agents builtin-tools toggle off memory agents builtin-tools toggle on
memory agents builtin-tools toggle [tool-id] [on|off] [flags]
-h, --help help for toggle
Create a new agent
Create a new runtime agent for the current project.
Examples: memory agents create --name "my-agent" --project memory agents create --name "cron-agent" --trigger-type schedule --cron "0 */5 * * * *" memory agents create --name "reaction-agent" --trigger-type reaction --reaction-events created,updated --reaction-object-types document
memory agents create [flags]
--cron string Cron schedule (e.g., '0 */5 * * * *')
--description string Agent description
--enabled string Enable agent (true/false)
--execution-mode string Execution mode
-h, --help help for create
--name string Agent name (required)
--prompt string Agent prompt
--reaction-events string Comma-separated reaction event types (e.g., created,updated)
--reaction-object-types string Comma-separated reaction object types (e.g., document,chunk)
--strategy-type string Strategy type (e.g., graph_object_processor)
--trigger-type string Trigger type (manual, schedule, reaction, webhook)
Delete an agent
Delete an agent by ID.
Prints "Agent deleted successfully." on success.
memory agents delete [id] [flags]
-h, --help help for delete
Get details for a specific run
Get full details for a specific agent run by its run ID. Output includes:
No --project flag is required — run IDs are globally unique.
This is the primary command to check the cost of a specific agent run.
memory agents get-run [run-id] [flags]
-h, --help help for get-run
--json Output result as JSON
Get agent details
Get full details for a specific agent by its ID.
Prints Name, ID, Project ID, Strategy Type, Enabled status, Trigger Type, Execution Mode, Cron Schedule (if set), Description (if set), Prompt (if set), Reaction Config (Object Types and Events), Last Run At, Last Run Status, Created At, Updated At, and any extra Config JSON.
memory agents get [id] [flags]
-h, --help help for get
Manage agent webhook hooks
Commands for managing webhook hooks on agents (create, list, delete)
-h, --help help for hooks
Create a webhook hook
Create a new webhook hook for an agent. The plaintext token is only shown once.
Examples: memory agents hooks create --label "CI/CD Pipeline" memory agents hooks create --label "Staging" --rate-limit 30 --burst-size 5
memory agents hooks create [agent-id] [flags]
--burst-size int Burst size for rate limiting (0 = server default)
-h, --help help for create
--label string Hook label (required)
--rate-limit int Rate limit in requests per minute (0 = server default)
Delete a webhook hook
Delete a webhook hook from an agent
memory agents hooks delete [agent-id] [hook-id] [flags]
-h, --help help for delete
List webhook hooks
List all webhook hooks configured for an agent.
Prints a numbered list with each hook's Label, ID, Enabled status, Rate Limit configuration (requests/minute and burst size, if set), and Created timestamp.
memory agents hooks list [agent-id] [flags]
-h, --help help for list
List all agents
List all agents configured for the current project.
Prints a numbered list with each agent's Name, ID, Enabled status, Trigger Type, Cron schedule (if any), Description (if set), Last Run timestamp, and Last Run Status. Use --project to specify a project other than the active one.
memory agents list [flags]
-h, --help help for list
Manage MCP servers
Commands for managing Model Context Protocol (MCP) servers in the Memory platform
-h, --help help for mcp-servers
Configure a tool's runtime settings
Set runtime configuration key/value pairs for a named MCP tool.
The command searches all MCP servers in the current project to find the tool by name, then patches its config with the provided key=value pairs.
Examples: memory agents mcp-servers configure brave_web_search api_key=YOUR_KEY --project memory agents mcp-servers configure reddit_search client_id=YOUR_ID client_secret=YOUR_SECRET --project
memory agents mcp-servers configure [tool-name] [key=value ...] [flags]
-h, --help help for configure
Create a new MCP server
Register a new MCP server with the specified configuration.
Examples: memory agents mcp-servers create --name "my-server" --type sse --url "http://localhost:8080/sse" memory agents mcp-servers create --name "stdio-server" --type stdio --command "npx" --args "-y,@modelcontextprotocol/server-github" memory agents mcp-servers create --name "my-server" --type http --url "http://localhost:8080/mcp" --env "API_KEY=abc123"
memory agents mcp-servers create [flags]
--args string Comma-separated arguments (for stdio type)
--command string Command to run (for stdio type)
--description string Server description
--enabled string Enable server (true/false, default: true)
--env strings Environment variables (KEY=VALUE format, can be specified multiple times)
-h, --help help for create
--name string Server name (required)
--type string Server type: 'sse', 'stdio', or 'http' (required)
--url string Server URL (for sse/http types)
Delete an MCP server
Remove an MCP server and all its tools from your project configuration
memory agents mcp-servers delete [server-id] [flags]
-h, --help help for delete
Get MCP server details
Get full details for a specific MCP server, including its registered tools.
Prints Name (enabled/disabled), ID, Project ID, Description (if set), Type, URL (for sse/http), Command and Args (for stdio), Env Vars count, Headers count, Created, and Updated timestamps. Also lists all registered tools with their enabled/disabled state and description (truncated to 60 characters).
memory agents mcp-servers get [server-id] [flags]
-h, --help help for get
Inspect an MCP server
Test connection to an MCP server and display its capabilities, tools, prompts, and resources
memory agents mcp-servers inspect [server-id] [flags]
-h, --help help for inspect
List all MCP servers
List all MCP servers configured for the current project.
Prints a numbered list with each server's Name (enabled/disabled), Description (if set), ID, Type (sse/http/stdio), URL or Command, Tool count, and Created timestamp.
memory agents mcp-servers list [flags]
-h, --help help for list
Sync tools from an MCP server
Connect to the MCP server and refresh the list of available tools
memory agents mcp-servers sync [server-id] [flags]
-h, --help help for sync
List tools for an MCP server
List all tools registered for a specific MCP server.
Each tool entry shows its enabled/disabled state and tool name. Use 'memory agents mcp-servers sync ' first to discover available tools if the list is empty.
memory agents mcp-servers tools [server-id] [flags]
-h, --help help for tools
Manage agent questions
Commands for listing and responding to agent questions
-h, --help help for questions
List questions for a project
List all agent questions for the current project.
Outputs the full question list as indented JSON. Use --status to filter by question status (e.g. pending, answered).
memory agents questions list-project [flags]
-h, --help help for list-project
--status string Filter by status (pending, answered, cancelled, expired)
List questions for a run
List all questions asked by the agent during a specific run.
Outputs the full question list as indented JSON, including each question's ID, status, prompt text, and response (if already answered).
memory agents questions list [run-id] [flags]
-h, --help help for list
Respond to a question
Respond to a pending agent question and resume the paused agent run.
Sends the response text as the answer to the specified question. Outputs the updated question record as indented JSON on success.
memory agents questions respond [question-id] [response] [flags]
-h, --help help for respond
List agent runs
List recent runs for an agent. Each run entry shows:
Use --limit to control how many runs are returned (default 10). Use "memory agents get-run [run-id]" to get the full breakdown for a specific run.
memory agents runs [id] [flags]
-h, --help help for runs
--limit int Maximum number of runs to return (default 10)
Trigger an agent run
Trigger an immediate run of an agent.
Prints "Agent triggered successfully!" with an optional message on success, or "Agent trigger failed." with an error message on failure.
memory agents trigger [id] [flags]
-h, --help help for trigger
Update an agent
Update an existing agent (partial update)
memory agents update [id] [flags]
--cron string New cron schedule
--description string New description
--enabled string Enable/disable (true/false)
--execution-mode string New execution mode
-h, --help help for update
--name string New agent name
--prompt string New agent prompt
--trigger-type string New trigger type
Ask the Memory CLI assistant a question or request a task
Ask the Memory CLI assistant a question or request a task.
The assistant is context-aware — it adapts its responses based on whether you are authenticated and whether a project is configured:
• Not authenticated → documentation answers; explains how to log in • Auth, no project → account-level tasks + documentation answers • Auth + project active → full task execution + documentation answers
The assistant fetches live documentation from the Memory docs site to answer questions about the CLI, SDK, REST API, agents, and knowledge graph features. It can also execute tasks on your behalf (list agents, query the graph, etc.).
Examples: memory ask "what are native tools?" memory ask "what agents do I have configured?" memory ask "how do I create a schema?" memory ask --project abc123 "list all agent runs from today" memory ask "what commands are available for managing API tokens?"
memory ask <question> [flags]
-h, --help help for ask
--json Output result as JSON {question, response, tools, elapsedMs}
--project string Project ID (optional — uses default project if configured)
--runtime string Sandbox runtime for scripting tasks: python (default) or go
--show-time Show elapsed time at the end of the response
--show-tools Show tool calls made by the assistant during reasoning
--v2 Use the v2 code-generation agent (fewer round-trips, faster)
Apply Blueprints (packs, agents, seed data) from a directory or GitHub URL
Apply Blueprints — schemas, agent definitions, skills, and seed data — to the current project from a structured directory or a GitHub repository URL.
The source directory (or GitHub repo root) may contain: packs/ — one file per memory schema (.json, .yaml, .yml) agents/ — one file per agent definition (.json, .yaml, .yml) skills/ — one subdirectory per skill, each containing a SKILL.md file seed/objects/ — per-type JSONL files with graph objects to seed seed/relationships/ — per-type JSONL files with graph relationships to seed
Skills follow the agentskills.io open standard: each skill is a directory with a SKILL.md file containing YAML frontmatter (name, description) and Markdown content.
By default the command is additive-only: existing resources are skipped. Use --upgrade to update resources that already exist.
Use the dump subcommand to export an existing project's data as seed files:
memory blueprints dump
Examples:
memory blueprints ./my-config memory blueprints https://github.com/acme/memory-blueprints memory blueprints https://github.com/acme/memory-blueprints#v1.2.0 --upgrade memory blueprints ./my-config --dry-run memory blueprints dump ./exported
memory blueprints <source> [flags]
--dry-run Preview actions without making any API calls
-h, --help help for blueprints
--project string Project ID or name (overrides config/env)
--token string GitHub personal access token (for private repos); also read from MEMORY_GITHUB_TOKEN
--upgrade Update existing resources instead of skipping them
Export project graph objects and relationships as JSONL seed files
Export the current project's graph objects and relationships as per-type JSONL seed files that can be re-applied with "memory blueprints
".Output layout: /seed/objects/.jsonl /seed/relationships/.jsonl
Files exceeding 50 MB are automatically split: .001.jsonl, .002.jsonl, …
Examples:
memory blueprints dump ./exported memory blueprints dump ./exported --types Document,Person memory blueprints dump ./exported --project my-project
memory blueprints dump <output-dir> [flags]
-h, --help help for dump
--project string Project ID or name (overrides config/env)
--types string Comma-separated list of object/relationship types to export (default: all types)
Interactive TUI for browsing projects and documents
Launch an interactive terminal UI (TUI) for browsing projects, documents, and extractions.
The TUI provides:
Minimum terminal size: 80x24
The Traces tab connects to the Grafana Tempo instance that runs alongside the configured server. The Tempo URL is derived automatically from the server URL (same host, port 3200). Override with --tempo-url or MEMORY_TEMPO_URL if Tempo runs elsewhere.
memory browse [flags]
-h, --help help for browse
--tempo-url string Override Tempo URL (auto-derived from server URL by default)
Generate shell completion scripts
Generate shell completion scripts for Memory CLI.
The completion script provides:
To load completions:
Bash: $ source <(memory completion bash)
$ memory completion bash > /etc/bash_completion.d/memory
$ memory completion bash > $(brew --prefix)/etc/bash_completion.d/memory
Zsh:
$ echo "autoload -U compinit; compinit" >> ~/.zshrc
$ memory completion zsh > "${fpath[1]}/_memory"
Fish: $ memory completion fish | source
$ memory completion fish > ~/.config/fish/completions/memory.fish
PowerShell: PS> memory completion powershell | Out-String | Invoke-Expression
PS> memory completion powershell > memory.ps1
Notes:
memory completion [bash|zsh|fish|powershell]
-h, --help help for completion
Manage CLI configuration
Configure server URL, credentials, and other settings for the Memory CLI
-h, --help help for config
Set the email for authentication
Set the email address used for authentication in the CLI configuration file.
Prints the email that was set and the path to the configuration file where the setting was saved.
memory config set-credentials [email] [flags]
--config string config file path
-h, --help help for set-credentials
Set the Memory server URL
Set the Memory server URL in the CLI configuration file.
Prints the new server URL and the path to the configuration file where the setting was saved. Use this to point the CLI at a different server environment (e.g. local dev vs production).
memory config set-server [url] [flags]
--config string config file path
-h, --help help for set-server
Set a configuration value
Set a configuration value by key.
Supported keys: server_url Server URL (e.g., http://localhost:3002) api_key API key for authentication email Email for authentication org_id Organization ID project_id Project ID google_api_key Google API key (standalone installations only)
For standalone installations, google_api_key is saved to .env.local. All other keys are saved to config.yaml.
memory config set <key> <value> [flags]
--config string config file path
-h, --help help for set
Display current configuration
Display the current CLI configuration as a table.
Prints a Setting/Value table with: Server URL, API Key (masked, showing only the first 8 and last 4 characters), Email, Organization ID, Project ID, Debug mode, and the Config File path. Values are merged from the config file and any overriding environment variables.
memory config show [flags]
--config string config file path
-h, --help help for show
Manage project documents
Commands for managing documents in the Memory platform
-h, --help help for documents
--output string Output format: table or json (default "table")
--project string Project ID (overrides config/env)
Delete a document
Delete a document and all related entities.
Prints the deletion status and a summary of removed entities: Chunks, Extraction jobs, Graph objects, and Graph relationships. Use --output json for a machine-readable response.
memory documents delete <id> [flags]
-h, --help help for delete
Get a document by ID
Get details for a specific document by its ID.
Prints ID, Filename, MIME Type, Size (bytes), Conversion Status, total Chunks, Embedded Chunks, and Created/Updated timestamps. Use --output json to receive the full document record as JSON instead.
memory documents get <id> [flags]
-h, --help help for get
List documents
List documents in the current project.
Output is a table with columns: ID, Filename, MIME Type, Size (bytes), and Created date. Use --limit to control how many records are returned. Use --output json to receive the full document list as JSON.
memory documents list [flags]
-h, --help help for list
--limit int Maximum number of results (default 50)
Upload a file as a document
Upload a local file and create a document record. Use --auto-extract to trigger extraction after upload.
memory documents upload <file> [flags]
--auto-extract Trigger extraction after upload
-h, --help help for upload
Manage embedding workers
Inspect and control the embedding workers running in the Memory server.
Useful for benchmarking: pause all workers before a bench run so embeddings don't interfere with write throughput, then resume afterwards.
Examples: memory embeddings status Show current worker state memory embeddings pause Pause all embedding workers memory embeddings resume Resume all embedding workers memory embeddings pause --server http://your-server:3002
--config-path string path to Memory config.yaml
-h, --help help for embeddings
--server string Memory server URL (overrides config)
Get or set embedding worker config (batch, concurrency, stale-minutes)
Get or update embedding worker configuration at runtime without restarting.
All flags are optional — omit a flag to leave that value unchanged. With no flags, shows the current configuration.
Examples: memory embeddings config Show current config memory embeddings config --batch 200 --concurrency 200 Max throughput memory embeddings config --stale-minutes 60 Raise stale threshold memory embeddings config --batch 10 --concurrency 10 Throttle down
memory embeddings config [flags]
--batch int Number of jobs to dequeue per poll (0 = no change)
--concurrency int Number of jobs processed concurrently per poll (0 = no change)
-h, --help help for config
--interval-ms int Polling interval in milliseconds (0 = no change)
--stale-minutes int Minutes before a processing job is marked stale (0 = no change)
Pause all embedding workers (object, relationship, sweep)
Pause all embedding workers (objects, relationships, and sweep).
Prints a confirmation message from the server, then displays the updated worker state table showing each worker's status symbol (running ●, paused ⏸, stopped ○) and the current Config (batch_size, concurrency, interval_ms, stale_minutes).
memory embeddings pause [flags]
-h, --help help for pause
Resume all embedding workers
Resume all paused embedding workers (objects, relationships, and sweep).
Prints a confirmation message from the server, then displays the updated worker state table showing each worker's status symbol (running ●, paused ⏸, stopped ○) and the current Config (batch_size, concurrency, interval_ms, stale_minutes).
memory embeddings resume [flags]
-h, --help help for resume
Show pause/run state of all embedding workers
Show the current state of all embedding workers.
Prints a worker state table for the objects, relationships, and sweep workers. Each worker is shown with a symbol indicating its state: running (●), paused (⏸), or stopped (○). Also displays the current worker Config: batch_size, concurrency, interval_ms, and stale_minutes.
memory embeddings status [flags]
-h, --help help for status
Manage graph objects and relationships
Commands for managing graph objects and relationships in the Memory knowledge graph
-h, --help help for graph
--output string Output format: table or json (default "table")
--project string Project ID (overrides config/env)
Manage graph objects
-h, --help help for objects
Batch-create graph objects from a JSON file
Create multiple graph objects in one API call.
The input file must contain a JSON array of objects, each with: type (string, required) name (string, optional) — placed in properties.name description (string, optional) — placed in properties.description properties (object, optional) — arbitrary additional properties
Example objects.json: [ {"type": "Person", "name": "Alice"}, {"type": "Person", "name": "Bob", "description": "A developer"}, {"type": "Project", "name": "Acme", "properties": {"status": "active"}} ]
Output (one line per object):
memory graph objects create-batch [flags]
--file string Path to JSON file containing array of objects (required)
-h, --help help for create-batch
Create a graph object
Create a new graph object with the given type and optional properties
memory graph objects create [flags]
--description string Set properties.description
-h, --help help for create
--name string Set properties.name
--properties string JSON properties object
--type string Object type (required)
Delete a graph object
Soft-delete a graph object by ID
memory graph objects delete <id> [flags]
-h, --help help for delete
Show edges (relationships) for an object
Show all incoming and outgoing relationships for a graph object.
Prints two sections: Outgoing (format: [Type] → DstID (entity: EntityID)) and Incoming (format: [Type] ← SrcID (entity: EntityID)) with counts for each. Use --output json to receive the full edges response as JSON.
memory graph objects edges <id> [flags]
-h, --help help for edges
Get a graph object by ID
Get details for a graph object (entity) by its ID.
Prints Entity ID, Version ID, Type, Version number, Key (if set), Status (if set), Labels (if any), Created timestamp, and Properties as formatted JSON. Use --output json to receive the full object as JSON instead.
memory graph objects get <id> [flags]
-h, --help help for get
--output string Output format: table or json (default "table")
List graph objects
List graph objects (entities) in the current project.
Output is a table with columns: Entity ID, Type, Version, Status, and Created date. Use --type to filter by object type, --limit to control result count, and --output json to receive the full list as JSON.
memory graph objects list [flags]
-h, --help help for list
--limit int Maximum number of results (default 50)
--type string Filter by object type
Update a graph object
Update a graph object's properties or status (creates a new version)
memory graph objects update <id> [flags]
-h, --help help for update
--properties string JSON properties object to merge
Manage graph relationships
-h, --help help for relationships
Batch-create graph relationships from a JSON file
Create multiple graph relationships in one API call.
The input file must contain a JSON array of objects, each with: type (string, required) — relationship type from (string, required) — source entity ID to (string, required) — destination entity ID properties (object, optional)
Example relationships.json: [ {"type": "knows", "from": "", "to": ""}, {"type": "manages", "from": "", "to": ""} ]
Output (one line per relationship): ->
memory graph relationships create-batch [flags]
--file string Path to JSON file containing array of relationships (required)
-h, --help help for create-batch
Create a relationship
Create a directed relationship between two graph objects
memory graph relationships create [flags]
--from string Source object ID (required)
-h, --help help for create
--properties string JSON properties object
--to string Destination object ID (required)
--type string Relationship type (required)
Delete a relationship
Soft-delete a graph relationship by ID
memory graph relationships delete <id> [flags]
-h, --help help for delete
Get a relationship by ID
Get details for a graph relationship by its ID.
Prints Entity ID, Version ID, Type, From (source entity ID), To (destination entity ID), Version number, Created timestamp, and Properties as formatted JSON. Use --output json to receive the full relationship as JSON instead.
memory graph relationships get <id> [flags]
-h, --help help for get
List relationships
List relationships in the current project.
Output is a table with columns: Entity ID, Type, From (source entity ID), To (destination entity ID), and Created date. Use --type to filter by relationship type, --from/--to to filter by endpoint, --limit to control result count, and --output json to receive the full list as JSON.
memory graph relationships list [flags]
--from string Filter by source object ID
-h, --help help for list
--limit int Maximum number of results (default 50)
--to string Filter by destination object ID
--type string Filter by relationship type
Initialize a Memory project in the current directory
Interactive wizard that sets up a Memory project in the current directory.
Walks through:
Writes MEMORY_PROJECT_ID, MEMORY_PROJECT_NAME, and MEMORY_PROJECT_TOKEN to .env.local and auto-adds .env.local to .gitignore.
Running 'memory init' again detects existing configuration and offers to verify or reconfigure each step.
Use --skip-provider or --skip-skills to skip individual steps.
memory init [flags]
-h, --help help for init
--skip-provider skip LLM provider configuration step
--skip-skills skip Memory skills installation step
Install Memory skills to .agents/skills/
Install the built-in Memory skills from the embedded catalog into .agents/skills/ in the current directory (or the directory specified by --dir).
Only skills with the "memory-" prefix are installed. This is the set of skills that teach AI agents how to use the Memory CLI and platform.
By default the command skips skills that already exist. Use --force to overwrite existing skill directories.
memory install-memory-skills [flags]
--dir string target directory (default: .agents/skills relative to cwd)
--force overwrite existing skill directories
-h, --help help for install-memory-skills
Sign in or create a Memory account
Authenticate using the OAuth Device Authorization flow.
Opens your browser so you can sign in or create a new account. Your credentials are saved locally for future CLI use.
If this server is running in standalone mode, use an API key instead: memory config set-api-key
memory login [flags]
-h, --help help for login
Clear stored credentials
Remove locally stored OAuth credentials and log out from the Memory platform.
Before deleting local credentials, attempts to revoke tokens server-side via the OIDC revocation endpoint. Revocation is best-effort — if it fails, local credentials are still removed.
Use --all to also clear api_key and project_token from your config file, removing all locally stored authentication state.
memory logout [flags]
--all Also clear api_key and project_token from config
-h, --help help for logout
Show MCP configuration for AI agents
Print ready-to-use MCP server configuration snippets for connecting AI agents to Memory.
Outputs JSON configuration blocks for Claude Desktop, Cursor, and other MCP- compatible clients. Snippets use the active server URL and API key (project token takes precedence over account key). Copy the relevant block into your AI client's MCP configuration to enable Memory tools.
memory mcp-guide [flags]
-h, --help help for mcp-guide
Manage projects
Commands for managing projects in the Memory platform
-h, --help help for projects
Create a new API token for a project
Create a new project-scoped API token (emt_...) and print it.
The token is also written to .env.local in the current directory as MEMORY_PROJECT_TOKEN so subsequent CLI commands pick it up automatically.
Scopes default to: data:read data:write schema:read agents:read agents:write
Example: memory projects create-token my-project --name onboard-token
memory projects create-token [project-name-or-id] [flags]
-h, --help help for create-token
--name string Token name (default "cli-token")
--no-env Do not write token to .env.local
--scopes strings Token scopes (default: data:read,data:write,schema:read,agents:read,agents:write)
Create a new project
Create a new project in the Memory platform.
Prints the new project's Name and ID on success. If no LLM provider credentials are configured for the organization, a warning is shown explaining that AI features (embeddings, search, extraction) will not work until a provider is added via 'memory provider configure'.
memory projects create [flags]
--description string Project description
-h, --help help for create
--name string Project name (required)
--org-id string Organization ID (auto-detected if not specified)
Delete a project
Permanently delete a project and all its data
memory projects delete [project-id] [flags]
-h, --help help for delete
Get project details
Get details for a specific project by name or ID.
Prints the project's Name, ID, and Org ID. If a project info document is set it is shown as well. Use the --stats flag to additionally display counts for Documents, Graph Objects, Relationships, Extraction jobs, and installed Schemas with their object and relationship type names.
memory projects get [name-or-id] [flags]
-h, --help help for get
--stats Include project statistics (documents, objects, jobs, schemas)
List all projects
List all projects you have access to.
Output prints a numbered list with each project's Name and ID. If the project has a project info document set, it is shown beneath the name. Use the --stats flag to also display per-project counts for Documents, Graph Objects, Relationships, Extraction jobs (total/running/queued), and installed Schemas (with their object and relationship type names).
memory projects list [flags]
--filter string Filter results (e.g., 'name=MyProject,status=active')
-h, --help help for list
--limit int Maximum number of results (default from config)
--offset int Number of results to skip
--search string Search projects by name or description
--sort string Sort results (e.g., 'name:asc' or 'updated_at:desc')
--stats Include project statistics (documents, objects, jobs, schemas)
Set a monthly spend budget for a project
Set or clear the monthly spend budget for a project.
When the project's estimated spend for the current month exceeds budget_usd * budget_alert_threshold (default 0.8), an in-app notification is sent to all org members. Set --budget 0 to clear an existing budget.
Examples: memory projects set-budget my-project --budget 50 memory projects set-budget my-project --budget 100 --threshold 0.9 memory projects set-budget --budget 25
memory projects set-budget [project-name-or-id] [flags]
--budget float Monthly budget in USD (set to 0 to clear)
-h, --help help for set-budget
--threshold float Alert threshold as a fraction of budget (e.g. 0.8 = 80%) (default 0.8)
Set the project info document
Set the project info document — a Markdown description of this project's purpose, goals, audience, and context. Agents and MCP clients read this via the get_project_info tool to orient themselves before working with the project's data.
Provide content via --file (read a .md file) or --text (inline string). If no project is specified, the active project from config/env is used.
Examples: memory projects set-info --file README.md memory projects set-info my-project --file docs/project-info.md memory projects set-info --text "This project tracks internal HR documents."
memory projects set-info [project-name-or-id] [flags]
--file string Path to a Markdown file to use as project info
-h, --help help for set-info
--text string Inline project info text
Configure the LLM provider for a project
Configure the LLM provider credentials for a specific project.
Supported providers: google, google-vertex. Prints the provider name, the configured generative model, and the embedding model on success. Use flags such as --api-key, --embedding-model, and --generative-model to specify credentials and model overrides.
memory projects set-provider [project-name-or-id] <provider> [flags]
--api-key string Google AI API key (for google)
--embedding-model string Override embedding model for this project
--gcp-project string GCP project ID (for google-vertex)
--generative-model string Override generative model for this project
-h, --help help for set-provider
--location string GCP region (for google-vertex)
--sa-file string Path to Vertex AI service account JSON (for google-vertex)
Set active project
Set the active project context.
Updates project_id in ~/.memory/config.yaml and writes MEMORY_PROJECT_ID, MEMORY_PROJECT_NAME, and MEMORY_PROJECT_TOKEN into .env.local in the current directory so that subsequent CLI commands and application code automatically use the selected project. If no existing token is found for the project, a new one is created automatically. Run without arguments to select interactively from a numbered list of available projects.
Use --clear to remove the active project from the global config.
memory projects set [name-or-id] [flags]
--clear Clear the active project from config
-h, --help help for set
Manage LLM provider credentials and models
Commands for managing LLM provider credentials, model selections, and usage reporting.
-h, --help help for provider
Save project-level LLM provider credentials (overrides org config)
Save project-specific credentials and model selections for the given provider. This overrides the organization's provider config for this project.
Use --remove to remove the project-level override and fall back to the org config.
Supported providers: google — Google AI (Gemini API); requires --api-key google-vertex — Google Cloud Vertex AI; requires --gcp-project, --location
The project is read from --project or the MEMORY_PROJECT_ID environment variable.
Examples: memory provider configure-project google --api-key AIzaSy... memory provider configure-project google-vertex --gcp-project my-proj --location us-central1 --key-file sa.json memory provider configure-project google --remove
memory provider configure-project <provider> [flags]
--api-key string API key (required for google)
--embedding-model string Embedding model to use (auto-selected from catalog if omitted)
--gcp-project string GCP project ID (required for google-vertex)
--generative-model string Generative model to use (auto-selected from catalog if omitted)
-h, --help help for configure-project
--key-file string Path to service account JSON key file (google-vertex)
--location string GCP region, e.g. us-central1 (required for google-vertex)
--project string Project ID (auto-detected from MEMORY_PROJECT_ID)
--remove Remove the project-level override and inherit org config
Save LLM provider credentials and model selections for the organization
Save LLM provider credentials (and optionally model selections) for the current organization. Runs a live credential test and syncs the model catalog on success. Models are auto-selected from the catalog if not specified.
Supported providers: google — Google AI (Gemini API); requires --api-key google-vertex — Google Cloud Vertex AI; requires --gcp-project, --location Optionally supply --key-file for a service account JSON key.
Examples: memory provider configure google --api-key AIzaSy... memory provider configure google-vertex --gcp-project my-project --location us-central1 --key-file sa.json memory provider configure google --api-key AIzaSy... --generative-model gemini-2.5-flash --embedding-model text-embedding-004
memory provider configure <provider> [flags]
--api-key string API key (required for google)
--embedding-model string Embedding model to use (auto-selected from catalog if omitted)
--gcp-project string GCP project ID (required for google-vertex)
--generative-model string Generative model to use (auto-selected from catalog if omitted)
-h, --help help for configure
--key-file string Path to service account JSON key file (google-vertex)
--location string GCP region, e.g. us-central1 (required for google-vertex)
--org-id string Organization ID (auto-detected from config)
Show current provider configurations
List all configured LLM providers at the organization level, plus any project-level overrides across all projects in the organization.
The output is a table with columns: SCOPE, PROVIDER, GENERATIVE MODEL, EMBEDDING MODEL, GCP PROJECT, LOCATION, and UPDATED.
Examples: memory provider list memory provider list --org-id memory provider list --json
memory provider list [flags]
-h, --help help for list
--json Output raw JSON
--org-id string Organization ID (auto-detected from config)
List available models from the provider catalog
List models available in the cached model catalog.
Without a provider argument, lists models for all configured providers. Pass a provider name to filter to a single provider.
Use --type to filter by model type (embedding or generative).
Examples: memory provider models memory provider models google-vertex memory provider models google --type generative
memory provider models [provider] [flags]
-h, --help help for models
--org-id string Organization ID (auto-detected from config)
--type string Filter by model type: embedding or generative
Test LLM provider credentials with a live generate call
Send a live "say hello" generate call to verify that provider credentials work end-to-end.
Without a provider argument, tests all configured providers. Pass a provider name (google or google-vertex) to test a specific one.
Use --project to test using the project-level credential hierarchy (project override → org) instead of org credentials only.
Examples: memory provider test memory provider test google-vertex memory provider test google --project
memory provider test [provider] [flags]
-h, --help help for test
--org-id string Organization ID (auto-detected from config)
--project string Project ID for project-level credential resolution
Show LLM usage over time
Show LLM token usage and estimated cost broken down by time period.
Without --project, reports org-wide usage. With --project, reports usage for that specific project. Use --granularity to control bucket size (default: day).
Output is a table with columns: PERIOD, PROVIDER, MODEL, TEXT IN, IMAGE, VIDEO, AUDIO, OUTPUT, and EST. COST (USD). A running subtotal is shown per period.
Examples: memory provider timeseries memory provider timeseries --project --granularity week memory provider timeseries --since 2024-01-01 --until 2024-03-31 --granularity month
memory provider timeseries [flags]
--granularity string Time bucket size: day, week, or month (default "day")
-h, --help help for timeseries
--json Output raw JSON
--org-id string Organization ID (auto-detected from config)
--project string Filter to a specific project ID
--since string Start date (YYYY-MM-DD)
--until string End date (YYYY-MM-DD)
Show LLM usage and estimated cost
Show aggregated LLM token usage and estimated cost.
Without --project, reports org-wide usage across all projects. With --project, reports usage for that specific project.
Use --by-project to break org-wide totals down per project instead of per model.
Output is a table with columns: PROVIDER, MODEL, TEXT IN (tokens), IMAGE (tokens), VIDEO (tokens), AUDIO (tokens), OUTPUT (tokens), and EST. COST (USD). A total estimated cost line is printed below the table.
Examples: memory provider usage memory provider usage --project memory provider usage --since 2024-01-01 memory provider usage --by-project
memory provider usage [flags]
--by-project Break down org usage by project instead of by model
-h, --help help for usage
--json Output raw JSON
--org-id string Organization ID (auto-detected from config)
--project string Filter usage to a specific project ID
--since string Start date for usage window (YYYY-MM-DD)
--until string End date for usage window (YYYY-MM-DD)
Query a project using natural language
Query a project using natural language.
By default, uses the graph-query-agent — an AI agent that reasons over the knowledge graph using search, traversal, and entity tools. The agent is managed server-side; no agent ID is needed.
Use --mode=search for direct hybrid search without AI reasoning.
Examples: memory query "what are the main services and how do they relate?" memory query --mode=search "auth service" memory query --project abc123 "list all requirements"
memory query <question> [flags]
--debug Include debug information in output
--fusion-strategy string Fusion strategy: weighted, rrf, interleave, graph_first, text_first (search mode only) (default "weighted")
-h, --help help for query
--json Output results as JSON
--limit int Maximum number of results to return (search mode only) (default 10)
--mode string Query mode: agent (default, AI reasoning) or search (direct hybrid search) (default "agent")
--project string Project ID to query (uses default project if not specified)
--result-types string Types of results: graph, text, or both (search mode only) (default "both")
--show-scores Show relevance scores for each result (search mode only)
--show-time Show elapsed query time
--show-tools Show tool calls made by the agent (agent mode only)
Manage schemas
Commands for managing schemas in the Memory platform
-h, --help help for schemas
--output string Output format: table or json (default "table")
--project string Project ID (overrides config/env)
Show compiled object and relationship types for the current project
Show the merged set of type definitions compiled from all installed schemas.
Prints two tables: Object Types (columns: Name, Label, Schema, Description) and Relationship Types (columns: Name, Label, Source → Target, Schema). Use --output json to receive the raw compiled types as JSON.
memory schemas compiled-types [flags]
-h, --help help for compiled-types
Create a schema from a JSON file
Create a new schema by loading its definition from a JSON file
memory schemas create [flags]
--file string Path to schema JSON file (required)
-h, --help help for create
Delete a schema from the registry
Permanently delete a schema definition from the global registry
memory schemas delete <schema-id> [flags]
-h, --help help for delete
Get a schema by ID
Get details for a schema pack by its ID.
Prints ID, Name, Version, Description (if set), Author (if set), Draft status, and Created timestamp. Use --output json to receive the full schema record as JSON instead.
memory schemas get <schema-id> [flags]
-h, --help help for get
Install a schema into the current project
Install a schema into the current project.
Two modes: install Install an existing schema from the registry by ID. install --file schema.json Create a new schema from a JSON file and install it in one step.
memory schemas install [<schema-id>] [flags]
--dry-run Preview what would be installed without making changes
--file string Create schema from JSON file and install in one step
-h, --help help for install
--merge Additively merge incoming type schemas into existing registered types
List installed schemas
List schemas currently installed (assigned) on the current project.
Output is a table with columns: Assignment ID, Schema ID, Name, Version, Active (yes/no), and Installed date. The Assignment ID is used with 'memory schemas uninstall' to remove a schema from the project. Use --output json to receive the full list as JSON.
memory schemas installed [flags]
-h, --help help for installed
List available schemas
List schemas available in the global registry for the current project to install.
Output is a table with columns: ID, Name, Version, and Description (truncated to 60 characters). Use --output json to receive the full list as JSON.
memory schemas list [flags]
-h, --help help for list
Uninstall (remove) a schema assignment from the current project
Remove a schema assignment from the current project by its assignment ID.
Use 'memory schemas installed' to list assignment IDs. Prints "Schema assignment removed." on success.
memory schemas uninstall <assignment-id> [flags]
-h, --help help for uninstall
Manage a self-hosted Memory server
Commands for installing, running, and maintaining a self-hosted Memory server.
-h, --help help for server
Control Memory services
Control and manage Memory standalone services.
This command provides service management capabilities similar to memory-ctl:
Examples: memory ctl start memory ctl stop memory ctl status memory ctl logs -f memory ctl logs server memory ctl health
--dir string Installation directory (default "/root/.memory")
-h, --help help for ctl
Check server health
Check the health of the local Memory server.
Makes an HTTP GET request to the server's /health endpoint and prints whether the server is healthy (✓) or not responding (✗). On a healthy response the full JSON health payload is printed in indented format.
memory server ctl health [flags]
-h, --help help for health
Show service logs
Show logs from Memory services.
Examples: memory ctl logs # Show recent logs from all services memory ctl logs -f # Follow logs in real-time memory ctl logs server # Show logs from server only memory ctl logs -n 50 # Show last 50 lines
memory server ctl logs [service] [flags]
-f, --follow Follow log output
-h, --help help for logs
-n, --lines int Number of lines to show (default 100)
Pull latest Docker images
memory server ctl pull [flags]
-h, --help help for pull
Restart all services
memory server ctl restart [flags]
-h, --help help for restart
Open shell in server container
memory server ctl shell [flags]
-h, --help help for shell
Start all services
memory server ctl start [flags]
-h, --help help for start
Show service status
Show the current status of all Memory Docker services.
Runs 'docker compose ps' for the local installation and prints the container name, state (running/exited), and port mappings for each service.
memory server ctl status [flags]
-h, --help help for status
Stop all services
memory server ctl stop [flags]
-h, --help help for stop
Check system health and configuration
Run diagnostic checks on your Memory CLI installation.
This command verifies:
Use --fix to automatically repair common issues.
memory server doctor [flags]
--debug Show detailed debug information (copyable for bug reports)
--fix Attempt to automatically fix detected issues
-h, --help help for doctor
Install Memory standalone server
Install Memory standalone server with all required components.
This command will:
Example: memory install memory install --port 8080 --google-api-key YOUR_KEY memory install --dir /opt/memory --skip-start
memory server install [flags]
--dir string Installation directory (default "/root/.memory")
--force Overwrite existing installation
--google-api-key string Google API key for embeddings
-h, --help help for install
--port int Server port (default 3002)
--skip-start Generate config but don't start services
Remove Memory installation
Remove Memory standalone server installation.
This command will:
Example: memory uninstall memory uninstall --keep-data memory uninstall --force
memory server uninstall [flags]
--dir string Installation directory (default "/root/.memory")
--force Skip confirmation prompt
-h, --help help for uninstall
--keep-data Keep Docker volumes (preserve data)
Upgrade the standalone server installation
Upgrades the Memory standalone server installation.
This will:
Examples: memory server upgrade memory server upgrade --dir ~/.memory
memory server upgrade [flags]
--dir string Installation directory (default "/root/.memory")
-f, --force Force upgrade without confirmation
-h, --help help for upgrade
Save a static Bearer token as CLI credentials
Save a static Bearer token to ~/.memory/credentials.json.
Useful in CI, test harnesses, and dev environments where a token is pre-issued rather than obtained via the OAuth device flow.
Example: memory auth set-token e2e-test-user
memory set-token <bearer-token> [flags]
--duration string Token validity duration (default 24h, e.g. 48h, 168h)
-h, --help help for set-token
Manage skills
Commands for managing skills — reusable Markdown workflow instructions for agents
--global Use global scope (built-in skills only, superadmin)
-h, --help help for skills
--json Output as JSON
--org string Organization ID (creates/lists org-scoped skill)
--project string Project ID (creates/lists project-scoped skill)
Create a skill
Create a new skill. Use --project to create a project-scoped skill, or omit for global.
memory skills create [flags]
--content string Skill content (Markdown)
--content-file string Path to a file containing the skill content
--description string Skill description (required)
-h, --help help for create
--name string Skill name (slug, e.g. 'my-skill') (required)
Delete a skill by ID
Permanently delete a skill by its ID.
Prints "Skill deleted." on success. You will be prompted for confirmation unless the --confirm flag is provided.
memory skills delete [id] [flags]
--confirm Skip confirmation prompt
-h, --help help for delete
Get a skill by ID
Get full details for a skill by its ID.
Prints ID, Name, Description, Scope (global / org / project), Created and Updated timestamps, and the full skill Content. Use --json to receive the raw JSON response instead.
memory skills get [id] [flags]
-h, --help help for get
Import skills from a SKILL.md file or directory
Import one or more skills and register them on the server so agents can use them.
Import a single SKILL.md file: memory skills import path/to/SKILL.md
Import all skills found in a directory (scans one level deep for SKILL.md files): memory skills import --from-dir .agents/skills/
Auto-discover skills from well-known locations (.agents/skills/, ~/.claude/skills/, etc.): memory skills import --discover
Import all discovered skills without prompting: memory skills import --discover --all
Import built-in Memory skills from the embedded catalog: memory skills import --builtin
Import built-in skills including experimental ones: memory skills import --builtin --experimental
memory skills import [path] [flags]
--all Import all found skills without prompting
--builtin Import from the built-in embedded Memory skill catalog
--discover Auto-discover skills from well-known locations (.agents/skills/, ~/.claude/skills/, etc.)
--experimental Include experimental skills when importing from the built-in catalog (--builtin)
--from-dir string Scan a directory for SKILL.md files and import all found skills
-h, --help help for import
List skills installed on the server
List skills stored on the server and available to agents.
Output is a table with columns: NAME, DESCRIPTION (truncated to 55 characters), SCOPE (global/org/project), and ID. Use --project to include project-scoped skills, or --global for global-only skills. Use --json to receive the full skill list as JSON.
memory skills list [flags]
-h, --help help for list
Update a skill
Update the description or content of an existing skill.
Prints "Skill updated." followed by the skill's ID and Name on success. At least one of --description, --content, or --content-file must be provided. Use --json to receive the full updated skill as JSON instead.
memory skills update [id] [flags]
--content string New content (Markdown)
--content-file string Path to file with new content
--description string New description
-h, --help help for update
Show current authentication status
Display detailed information about the current authentication session and server health.
Shows authentication Mode (project token, account API key, or OAuth), Server URL, masked credential key, and connection Status (Connected or unreachable). Also displays server Health and Version. If authenticated as a user, prints the active project Name and ID, or a numbered list of all accessible projects.
Additionally prints full Usage Statistics for the active project including: Documents, Graph Objects, Relationships, Type Registry (Types, Enabled, TypesWithObjects), Template Packs, and Processing Pipeline job queue depths.
memory status [flags]
-h, --help help for status
Manage API tokens
Commands for managing API tokens (emt_* keys). Tokens can be account-level (cross-project) or project-scoped.
-h, --help help for tokens
--project string Project name or ID (omit for account-level tokens)
Create a new API token
Create a new API token.
Without --project, creates an account-level token usable across all projects. With --project, creates a project-scoped token.
On success, prints the full plaintext Token value prominently (this is the only time the full token is shown — save it immediately), followed by ID, Name, Type, Prefix, Scopes, and Created timestamp.
Valid scopes: schema:read, data:read, data:write, agents:read, agents:write, projects:read, projects:write
memory tokens create [flags]
-h, --help help for create
--name string Token name (required)
--scopes string Comma-separated scopes (default: data:read). Valid: schema:read, data:read, data:write, agents:read, agents:write, projects:read, projects:write
Get token details
Get details for a specific API token by its ID.
Use --project to specify a project-scoped token; without it, looks up an account-level token.
memory tokens get [token-id] [flags]
-h, --help help for get
List API tokens
List API tokens and their details.
Without --project, lists account-level tokens. With --project, lists tokens for the specified project. Each token entry prints: Name, ID, Prefix, Type (account or project), Scopes, Created timestamp, and Revoked timestamp (if applicable). For project tokens, the full plaintext token value is also fetched and displayed — treat this output as sensitive.
memory tokens list [flags]
-h, --help help for list
Revoke an API token
Permanently revoke an API token, making it unusable. Without --project, revokes an account-level token.
memory tokens revoke [token-id] [flags]
-h, --help help for revoke
Query traces
Query OpenTelemetry traces via the server's built-in Tempo proxy.
Traces are proxied through the configured --server endpoint so no direct access to Tempo is required.
-h, --help help for traces
Fetch a full trace by ID
Fetch and display a full trace as an indented span tree.
Prints the Trace ID, then each span in a tree structure showing the span name