NeoSQL MCP

What NeoSQL MCP MCP server does

NeoSQL MCP MCP server connects an MCP host to a running NeoSQL Desktop application. It does not act as an independent database server or command-line database client. Instead, the local package forwards requests to NeoSQL Desktop, which handles the configured database connections and project context.

The supported database list includes PostgreSQL, Supabase, MySQL, MariaDB, Oracle, SQL Server, SQLite, H2, and Databricks. The exact connection requirements depend on NeoSQL Desktop and the database system in use. A project must have MCP-enabled connections and schemas available in Desktop before the tools can provide database context.

How it works

The package runs as a local stdio MCP server inside the MCP host's process tree. It communicates with NeoSQL Desktop through JSON-RPC over a macOS Unix Domain Socket or a Windows Named Pipe. This local channel does not open a TCP port, and its endpoint cannot be changed through environment variables or configuration files.

MCP hosts receive schema information and query results from the server. Database access follows NeoSQL Desktop's MCP Access Control settings, while database credentials remain configured in Desktop rather than in each MCP host. The optional --project-id argument lets the server target a specific project; without it, app-dependent tools use the project currently selected in Desktop.

Setup and configuration

NeoSQL MCP MCP server requires macOS or Windows, Node.js 20 or later, NeoSQL Desktop installed on the same machine, and an MCP host that can launch stdio servers. No global package installation is required. Configure the host to run:

npx -y neosql-mcp

The README documents configurations for Claude Code, Codex, Gemini CLI, and Cursor. It also describes installation as a Claude Code or Claude Desktop Cowork plugin. For a fixed project, pass the project ID as an argument, such as --project-id=<your-project-id>; use the project ID rather than its display name.

Tools and capabilities

Available tools cover project discovery, schema inspection, database changes, and code generation:

• ping provides a lightweight health check, while get-mcp-session-id reports the upstream session identifier.
• list-connections shows MCP-enabled NeoSQL connections and schemas for the current project.
• get-context-help explains default and explicit project-target behavior.
• list-tables lists tables, and get-table-details returns columns, keys, indexes, and related metadata.
• erd-create-tables and erd-modify-tables create or change virtual ERD table models without changing the database.
• execute-query runs SQL, including DDL statements.
• generate-code writes source files for selected tables using template packs, required variables, and an output folder configured in Project Settings.

Limitations and notes

A running, connected NeoSQL Desktop installation is part of the operating model; the package does not replace Desktop. Sign-in, project access, confirmations, and database connection setup remain Desktop responsibilities. Project targeting also depends on a Desktop version that supports it, and unsaved Desktop changes may need to be saved or discarded before navigation.

Review SQL requests carefully because execute-query can run DDL. Review code-generation settings as well: generate-code may overwrite existing files without another confirmation dialog. The server's local transport does not determine how an MCP host handles returned schema data or query results; consult the project's privacy policy for data processing, storage, retention, and deletion details.