CLI Guide

The Daspire CLI calls the same Control API used by the MCP Gateway.

daspire auth login
daspire workspaces list --json
daspire connectors list --json
daspire connectors spec <connector_id> --json
daspire sources discover <source_id> --json
daspire pipelines get <pipeline_id> --json
daspire pipelines get <pipeline_id> --refresh-catalog --json
daspire pipelines prepare --file pipeline.json
daspire pipelines apply --file pipeline.json
daspire approvals list --json
daspire approvals approve <approval_id>
daspire sessions list --json
daspire sessions revoke <session_id>

Set a custom API base URL for local or staging environments:

export DASPIRE_API_BASE_URL=http://localhost:8888/daspire/api/control/v1
export DASPIRE_APP_URL=http://localhost:3000

All agent-friendly commands support --json.

pipelines get reads metadata by default. --refresh-catalog performs Native discovery for a Native-owned connection and publishes its catalog receipt. It preserves selected streams and leaves newly discovered reports unselected; it creates no sync job and changes no credentials or schedule. Saved Native sources with older specs do not need to be resaved to obtain this catalog capability. Unsupported image/protocol combinations fail explicitly.

For a new pipeline, use the exact catalogId from sources discover as source_catalog_id, with exact stream names and namespaces. For an existing pipeline, send only the intended selected streams/settings and retain omitted scheduling fields. The platform obtains authoritative schemas and revalidates the source and catalog when saving. Approval execution also refreshes the catalog; changed approved schemas require a new proposal. After an uncertain save response, read the pipeline and the approval result before submitting another change.

Approval Flow

Write commands create approval proposals. Review the proposal in Daspire or approve it from the CLI:

daspire approvals approve appr_123

Approval Flow​

Approval Flow