Developer tools
The Data Visions connector (MCP), the command line and the Module SDK: connect an AI app or coding agent, and build modules from outside the app.
Developer tools: the connector, the CLI and the SDKWhat the Data Visions connector, command line and Module SDK are, who uses which, how they fit together, and where to start.Read The Data Visions connector (MCP)How the Data Visions MCP connector works: its address, adding it to Claude, Claude Code, Cursor, Codex or ChatGPT, sign-in, workspaces, changes and audit.Read Connector tool referenceEvery built-in tool the Data Visions connector offers, what it does, whether it changes anything, and who can use it, plus how module tools work.Read Install and sign in to the CLIInstall the Data Visions command line (dv) for your own user without administrator rights, sign in, check your workspace, update it and fix common problems.Read CLI command referenceEvery dv command a workspace can use, grouped by job, with what each does, its main options, who can run it and whether it changes anything.Read The Module SDK: guides and references for coding agentsWhat the Module SDK contains, how a coding agent reads it through the connector, which skill or reference to open for each job, and how it stays current.Read Build a module with a coding agent, start to finishThe whole loop for Claude, Claude Code or Cursor: connect, read the SDK, plan, build, check, deploy to your workspace, test, ship new versions and submit to the Marketplace.Read Module manifest (module.json) referenceEvery section of a module's module.json: identity, permissions, tables and data migrations, agent, screens, services, schedules, outside systems and distribution.Read
Can't find what you need? Contact support.