---
title: External tools
description: Use the working API, MCP, and Git boundaries to read data and manage authored assets outside the app.
species: reference
---
# 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](/v2/docs/api/authentication) and the [Queries API](/v2/docs/api/queries).

## MCP

Use `https://mcp.supernova.ai/mcp` when an agent needs schema discovery and bounded read-only query execution. OAuth scopes separate file discovery from query execution. See [MCP access](/v2/docs/access/mcp).

## 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 and query | 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.