Menu
Use when connecting an agent client to ovstorage over MCP stdio and mapping common CLI workflows to MCP tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Deploy and develop against NVIDIA Omniverse Storage APIs on any Kubernetes cluster (MicroK8s, EKS, AKS, GKE, bare metal). Two storage adapters: (1) Example Storage Adapter — Python filesystem reference implementation + Discovery for learning and custom adapter development; (2) S3/Azure Production Storage Adapter — NVIDIA pre-built S3/Azure adapter + Discovery as minimum, expandable with Event Aggregation, Event Consumer, RabbitMQ, Envoy Auth Extension, Storage Navigator, and Contour ingress. Can deploy on the developer's behalf (generating scripts + .env) or guide manual deployment. Custom adapter development covers three APIs: Storage, Notifications, and Permissions. Use when a developer asks about deploying, configuring, validating, troubleshooting, or building any component of the Omniverse Storage APIs stack.
Use when adding or reviewing an authz plugin for ovstorage-broker or ovstorage-rest - covers the AuthzPlugin trait, the 21 operations, the policy-epoch model, and the cdylib cancellation contract.
Use when adding or reviewing a storage backend plugin for ovstorage.
Use when Rust changes affect ovstorage C or C++ headers and checked-in generated headers must be refreshed.
Use when starting an ovstorage-broker locally for development or integration testing - covers a minimal TOML, the cdylib plugin path, and how to hit the listener with broker-client or curl.
Use when checking the Storage API wire contract that ovstorage-plugin-services-client depends on.
| name | ovstorage-user-connect-via-mcp |
| description | Use when connecting an agent client to ovstorage over MCP stdio and mapping common CLI workflows to MCP tools. |
| license | CC-BY-4.0 |
| version | 0.1.0 |
| author | NVIDIA Omniverse |
| tags | ["ovstorage","mcp","agents"] |
| tools | ["Read"] |
| compatibility | Requires an ovstorage-mcp binary, configured plugins, and an MCP-capable agent client. |
Goal: Configure an agent client to spawn ovstorage-mcp, verify the
configured backends, then choose the MCP tool that matches the user's
storage task.
Register ovstorage-mcp as an MCP stdio server. Pass the same config
and plugin environment you would use with the CLI:
{
"command": "ovstorage-mcp",
"env": {
"OVSTORAGE_CONFIG": "/path/to/ovstorage.toml",
"OVSTORAGE_PLUGIN_DIR": "/path/to/plugins"
}
}
OVSTORAGE_CONFIG follows CLI precedence. If you intentionally want a
programmatic/no-config session, set OVSTORAGE_MCP_NO_CONFIG=1.
Call ovstorage_doctor before object I/O:
{
"tool": "ovstorage_doctor",
"arguments": {}
}
Confirm the desired backend kind is loaded and the target address root is visible before calling read/write/list tools.
| MCP tool | Closest CLI command | Notes |
|---|---|---|
ovstorage_doctor | ovstorage doctor --json | Health/config summary for agents. |
ovstorage_capabilities | ovstorage list-backends plus ovstorage list-routes | MCP reports one prefix. |
ovstorage_stat | ovstorage stat ADDRESS | Object info. |
ovstorage_list | ovstorage list PREFIX | Use next_page_token for pagination. |
ovstorage_read | ovstorage read ADDRESS | Requires max_bytes; bytes are base64. |
ovstorage_materialize | ovstorage read ADDRESS -o FILE | MCP returns a leased path, not a durable caller-owned copy. |
ovstorage_release | none | Releases a materialize lease. |
ovstorage_write | ovstorage write ADDRESS | Data is base64 in MCP. |
ovstorage_update_metadata | ovstorage update-metadata ADDRESS | Same precondition model. |
ovstorage_create_directory | ovstorage create-directory ADDRESS | Also CLI mkdir. |
ovstorage_copy | ovstorage cp SRC DEST | Source/destination preconditions are explicit. |
ovstorage_move | ovstorage mv SRC DEST | Also CLI rename. |
ovstorage_delete | ovstorage delete ADDRESS | Also CLI rm. |
ovstorage_delete_directory | ovstorage delete-directory ADDRESS | Recursive and dry-run are arguments. |
ovstorage_connections_list | ovstorage list-routes | MCP exposes configured connections. |
ovstorage_address_roots_list | ovstorage list-routes | MCP exposes visible address roots directly. |
MCP v0 does not expose diff, sync, list-versions,
get-latest-version, check-access, watch-directory, or cache/state
diagnostic commands such as cache-status, cache-doctor, and
state-status. Use the CLI for those workflows.
ovstorage_doctor responseok: false envelopesdocs/public/agent/mcp-tools.md
— full MCP tool reference