SuiteCloud Developer Assistant Now Supports AI Coding Assistant Integration via Local Proxy

What changed

SuiteCloud Developer Assistant (SDA) now supports integration with third-party AI coding assistants and other external tools. The latest version of SuiteCloud CLI for Node.js includes a dedicated command that starts a local proxy, allowing AI coding assistants to connect to SDA securely.

This means developers can use AI-powered code completion and generation tools alongside SDA's existing record/field metadata, SuiteScript API documentation, and script template capabilities.

Technical details

The release note is light on specifics. What we know:

• A new CLI command (name not specified in the source) starts a local proxy that bridges SDA and third-party tools.
• The connection is described as "secure," but no authentication mechanism or protocol details (e.g., MCP, LSP, REST) are documented in this note.
• This requires the latest version of SuiteCloud CLI for Node.js — the exact minimum version number is not stated.

Oracle points to a help topic titled Setting Up SuiteCloud Developer Assistant with Other Third-Party Tools and AI Coding Assistants for the actual setup procedure, but the release note itself does not detail the command syntax, supported protocols, or which AI tools have been validated.

What to do

1. Update SuiteCloud CLI for Node.js to the latest version: npm install -g @oracle/suitecloud-cli (or your preferred package manager). Verify the installed version includes the new proxy command.
2. Review the help topic Setting Up SuiteCloud Developer Assistant with Other Third-Party Tools and AI Coding Assistants in the NetSuite Help Center for the exact CLI command, supported protocols, and configuration options.
3. If you use AI coding assistants (e.g., GitHub Copilot, Cursor, or similar), test the local proxy integration in a sandbox environment to evaluate how SDA metadata surfaces in your AI tool's context.
4. Confirm any firewall or network policies allow the local proxy's port — the specific port/binding is not documented in this note, so check the help topic for defaults.