memory_get — Aziel Runtime MCP Tool
memory_get
(memory get) is one of 36 tools on the
Aziel Runtime
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call memory_get from your client
- Claude Code Aziel Runtime memory_get run in your project directory
- Claude Desktop Aziel Runtime memory_get ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aziel Runtime memory_get ~/.cursor/mcp.json
- VS Code Aziel Runtime memory_get .vscode/mcp.json
- Zed Aziel Runtime memory_get ~/.config/zed/settings.json
- Windsurf Aziel Runtime memory_get ~/.codeium/windsurf/mcp_config.json
- Cline Aziel Runtime memory_get ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aziel Runtime memory_get ~/.gemini/settings.json
- Grok Aziel Runtime memory_get .mcp.json (in your project root)
- ChatGPT Aziel Runtime memory_get Settings → Connectors → Advanced → Developer mode
- Claude.ai Aziel Runtime memory_get Settings → Connectors → Add custom connector
- LangChain Aziel Runtime memory_get pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aziel-runtime https://aziel-runtime.vibelock.workers.dev/mcpOther tools on this server
- runtime_skill
- fraggate_list
- fraggate_describe
- fraggate_verify
- fraggate_call
- decisiongate_check
- library_lookup
- mesh_status
- mesh_enable
- mesh_disable
- mesh_join
- mesh_heartbeat
- mesh_leave
- mesh_nodes
- mesh_broadcast
- chainlock_append
- chainlock_tip
- chainlock_recall
- chainlock_verify
- chainlock_seal
- memory_observe
- memory_resolve
- memory_calibrate
- memory_recall
- runtime_software
- runtime_bundle
- runtime_pull
- runtime_run
- runtime_manifest
- runtime_session_open
- runtime_session_policy
- runtime_session_exec
- runtime_session_receipt
- runtime_session_receipts
- runtime_session_close
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.