Connect AI Assistants with Nexo MCP

Database support

Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.

Supported databases and feature availability · Connection guides

Nexo SQL Studio lets supported AI clients use approved Oracle connections for SQL, PL/SQL, data models, and application development. This database integration is a Nexo Pro feature. Install the Nexo SQL Studio extension, activate Pro, and sign in to Nexo before using its MCP tools. AI usage is not included in Nexo Pro: Nexo AI and other AI clients run on your own ChatGPT or Claude subscription, or on your own API keys, and that provider bills the usage.

The local Nexo MCP companion supplies the tools to external clients. It can remain available after VS Code closes, but the connections, sign-in, license, and access rules still come from Nexo. No public MCP URL is needed for the local integration.

Prepare Nexo

1. Open your Oracle workspace in Nexo SQL Studio and sign in with an active Pro license.
2. In Connections, right-click each connection you want to expose and choose Configure MCP access. Select read-only or read/write access as appropriate. Connections with MCP access disabled are unavailable to AI.
3. Let Nexo finish startup so it can prepare or update the local integration. If the connector is missing or outdated, Nexo AI offers to install or update it above the message box; you can also choose Install Nexo connector from the Nexo AI settings (gear) menu.
4. Start a new session in the AI client and ask it to check nexo_status before working with database data.

Choose your AI client

Codex

Nexo prepares the local plugin, but you install it in Plugins > Personal. Start a new task and select Nexo SQL Studio if needed. Codex is available on the ChatGPT Free plan, subject to usage limits.

Cursor

Nexo prepares the local plugin. Reload the Cursor window, then find or enable Nexo SQL Studio in Customize > Plugins. Start a new chat and ask for nexo_status.

Claude Code CLI or Claude Desktop Code

Nexo installs and updates the local Claude Code plugin automatically. Start a new Code session and enable the plugin if you previously disabled it. Type / and search for nexo-connector, then choose /nexo-sql-studio:nexo-connector, or ask for nexo_status. Claude Code needs a paid Claude plan or API billing.

Claude Desktop Chat

Nexo registers a separate local MCP server for Desktop Chat. Fully quit and reopen Claude Desktop. In Chat, open + > Connectors and look for the local Nexo tools. This does not appear as a Claude account plugin.

GitHub Copilot in VS Code

Each Nexo window contributes its own VS Code MCP provider. Run MCP: List Servers and select Nexo, or restart Copilot CLI and check /mcp.

The Claude Code plugin’s local MCP tools do not work in regular Claude Chat or on claude.ai. Claude Desktop Chat uses the separate local registration described above; it is not available in Cowork. Client plugins and Desktop registrations are different installations.

Access and safety

Nexo only exposes connections for which you explicitly allow MCP access. Read and write permissions and confirmation rules are set per connection; a prompt cannot override them. Database credentials remain in Nexo’s local protected store, but results and metadata returned to an AI client may be sent to that client’s provider. Grant only the access needed for the task and review generated SQL and changes before applying them.

If you run production and debug Nexo side by side, sign in to each separately. User-level plugins connect to production Nexo; the debug window uses its own VS Code MCP provider and does not replace those plugins. A single AI session uses one authorized workspace, so start a separate session for another workspace.

For the full workflow, see AI-Assisted Development.