memory_resolve — Aziel Runtime MCP Tool
memory_resolve
(memory resolve) 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_resolve from your client
- Claude Code Aziel Runtime memory_resolve run in your project directory
- Claude Desktop Aziel Runtime memory_resolve ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aziel Runtime memory_resolve ~/.cursor/mcp.json
- VS Code Aziel Runtime memory_resolve .vscode/mcp.json
- Zed Aziel Runtime memory_resolve ~/.config/zed/settings.json
- Windsurf Aziel Runtime memory_resolve ~/.codeium/windsurf/mcp_config.json
- Cline Aziel Runtime memory_resolve ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aziel Runtime memory_resolve ~/.gemini/settings.json
- Grok Aziel Runtime memory_resolve .mcp.json (in your project root)
- ChatGPT Aziel Runtime memory_resolve Settings → Connectors → Advanced → Developer mode
- Claude.ai Aziel Runtime memory_resolve Settings → Connectors → Add custom connector
- LangChain Aziel Runtime memory_resolve 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_calibrate
- memory_recall
- memory_get
- 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.