Integrate with LeapView

LeapView exposes CLI, HTTP API, built-in agent, and remote MCP surfaces backed by the same active projects, authorization, data policies, and semantic contracts. Choose the highest-level stable operation that fits the integration.

Choose an integration surface

• Use the CLI for human-operated delivery, CI pipelines, managed-data synchronization, maintenance, and quick headless queries.
• Use the HTTP API for application integrations that need typed request, response, status, pagination, and compatibility contracts.
• Use Headless BI queries for governed dashboard or semantic-model results without the LeapView browser UI.
• Use Public and embedded dashboards for anonymous, governed dashboard presentations on approved origins.
• Use Agent integrations for iterative natural-language exploration through the governed tool catalog.
• Use the agent tool catalog reference when implementing direct MCP calls or evaluating agent tool traces.
• Use MCP to expose the same governed tools to Claude or another remote MCP host.

Design a reliable boundary

Read API conventions for authentication, resource identity, pagination, errors, retries, timeouts, cancellation, and compatibility. Use Automation and CI when the integration delivers projects unattended.

Every integration should use an attributable principal with the narrowest useful privileges. Read Service principals and API tokens for workload identity and credential handling, and Roles, grants, and policies for effective access.

Look up exact contracts

Use the generated CLI command reference and API reference for accepted syntax and schemas. Prefer those generated contracts over copying flags, paths, or payload shapes from an explanatory page.