External tools#
Supernova exposes 3 supported external boundaries: the public API for automation, MCP for agent tools, and Git for the organization data repo. Each boundary has a narrower credential than an interactive browser session.
Public API#
Use a personal access token or OAuth access token to submit queries, inspect resources, trigger supported actions, and retrieve results. API paths have no version segment. Additive fields can appear; breaking behavior requires a new contract rather than a silent path change.
Start with API authentication and the Queries API.
MCP#
Use https://mcp.supernova.ai/mcp for lake metadata, bounded read-only SQL,
organization data-repo files, and live dashboard authoring with signed visual
previews. OAuth scopes separate reads, writes, and query execution. See
MCP access.
Git#
Clone the organization data repo over its configured Git URL after adding an SSH key. Models, dashboards, themes, packages, and typesql.lock are ordinary reviewed files. A pushed commit becomes a new fixed repository revision for later runs.
Boundary summary#
| Need | Boundary | Credential |
|---|---|---|
| Query or automate resources | Public API | PAT or OAuth bearer |
| Let an agent inspect, query, and author dashboards | MCP | OAuth 2.1 scopes |
| Review authored assets locally | Git | Organization-authorized SSH key |
Direct storage credentials and internal service endpoints are not customer integration surfaces. Use the API result links for Parquet export instead of addressing storage objects yourself.