Data as of

MCP Toolbox for Databases for Cursor: Setup & Config

Cursor: MCP Toolbox for Databases connects agents and IDEs to enterprise data through prebuilt tools or custom query definitions.

What you can do with MCP Toolbox for Databases in Cursor

Use one database-tool framework for exploratory assistants and deliberately scoped production queries.

  • Explore database schemas from a coding assistant.
  • Group database tools into task-specific toolsets.
  • Observe database-tool activity with metrics and tracing.

Before you start: MCP Toolbox for Databases in Cursor

  • An MCP-compatible client
  • npx for this execution method
  • A PostgreSQL database for this example
  • Database-specific connection settings from the prebuilt reference

This is the README's prebuilt PostgreSQL example. Exact database connection environment variables are not stated in the supplied README, so none are invented here. Binaries and containers are recommended for a more standard installation. The repository is now named mcp-toolbox.

MCP Toolbox for Databases Cursor configuration

  1. Choose Cursor configuration scope

    For MCP Toolbox for Databases, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add MCP Toolbox for Databases to Cursor

    Use the genai-toolbox entry below in mcpServers. Keep MCP Toolbox for Databases's documented stdio connection fields and your other Cursor entries.

  3. Check MCP Toolbox for Databases in Cursor

    MCP Toolbox for Databases: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "genai-toolbox": {
      "command": "npx",
      "args": [
        "-y",
        "@toolbox-sdk/server",
        "--prebuilt=postgres",
        "--stdio"
      ],
      "env": {}
    }
  }
}

MCP Toolbox for Databases tools available to Cursor

MCP Toolbox for Databases's stored tool list documents 2 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

list_tables

Find list_tables under MCP Toolbox for Databases in Cursor's MCP settings; inspect its arguments when the agent requests a call.

execute_sql

Find execute_sql under MCP Toolbox for Databases in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Execute SQL through the database's prebuilt tool interface.

MCP Toolbox for Databases: full stored tool descriptions

Troubleshooting MCP Toolbox for Databases in Cursor

  • Cursor must find npx @toolbox-sdk/server (Node.js/npm) for MCP Toolbox for Databases. Enable the project/user entry in MCP settings and inspect its tools.
  • MCP Toolbox for Databases uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Connection configuration is database-specific and requires separate reference details.
  • Known limitation: The README characterizes npm execution as convenience-oriented rather than the most reliable installation.
  • Known limitation: Custom tools require source and query definitions.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

MCP Toolbox for Databases — details. Cursor guide

Frequently asked questions

Cursor's MCP Toolbox for Databases entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's genai-toolbox example uses stdio.

MCP Toolbox for Databases's Cursor configuration invokes npx @toolbox-sdk/server (Node.js/npm).

MCP Toolbox for Databases's stored list contains 2 tools, including list_tables, execute_sql. Compare those names with Cursor's connected tool list; the stored list is not a live check.

Yes. Toolsets group selected tools so they can be loaded together for particular applications or agents.

The README explains that genai-toolbox was renamed to mcp-toolbox, while the product is called MCP Toolbox for Databases.