NVIDIA Minerva MCP gives AI assistants authenticated, read-only access to NVIDIA Minerva observability data.
NVIDIA Minerva MCP is in beta.
Connect to the Endpoint
|
Endpoint |
Description |
Use it when |
|---|---|---|
|
|
Capability discovery and guarded Druid/Neo4j queries |
Your MCP client will select data and generate SQL or Cypher. |
After connecting, call tools/list and use only the tools the server returns.
Prerequisites
-
Open
https://<minerva-host>in a browser and sign in to NVIDIA Minerva at least once. -
Complete any required initial password change before authorizing the MCP client.
-
Production deployments require a trusted TLS certificate on the public HTTPS endpoint.
Connect from Claude Code
Add the endpoint to Claude Code:
claude mcp add --transport http minerva-mcp https://<minerva-host>/minerva/mcp
Then complete the authorization:
-
In Claude Code, run
/mcp. -
Select the NVIDIA Minerva connection and choose Authorize.
-
Sign in to NVIDIA Minerva in your browser and approve the connection.
-
Return to Claude Code and confirm the connection shows connected.
OAuth discovery and client registration are automatic; no client ID, client secret, database credentials, or backend token is required. The --transport http flag enables MCP Streamable HTTP and the endpoint remains protected by HTTPS.
Other MCP clients can connect using the same URL with their Streamable HTTP transport and browser OAuth flow.
Available Tools
The NVIDIA Minerva MCP exposes the following tools:
-
list_capabilitiesandget_capability_schemato discover the live NVIDIA Minerva data contract. -
druid_queryfor validated, read-only Druid SQL queries. -
get_neo4j_schemaandneo4j_queryfor validated, read-only topology queries when Neo4j is enabled for the deployment.
Security and Troubleshooting
-
All tools are read-only. NVIDIA Minerva MCP does not remediate issues or modify configurations.
-
Queries are validated and bounded before execution.
-
NVIDIA Minerva MCP is not tenant-aware. An authorized user can access all data in the deployment. Namespace and cluster query dimensions are filters, not per-user access controls.
Last updated: