How do I use multi-monetdb-mcp-server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@multi-monetdb-mcp-server list my MonetDB databases and show the schema of the analytics one" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

multi-monetdb-mcp-server

by cs-codespace

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

multi-monetdb-mcp-server

One MCP server for all your MonetDB databases.

A companion to multi-postgres-mcp-server, built for MonetDB column-store databases.

Documentation

Document	Audience	Contents
USAGE.md	AI agents & developers	Tool call sequences, decision flow, examples
config.example.json	Operators	Config file template
This README	Setup	Install, Cursor config, environment restriction

Related MCP server: mcp-postgres

Features

One server for all MonetDB databases
Config file with named labels (analytics, staging, …)
Dynamic connect — user provides credentials at runtime via mdb_connect
Hot reload — config changes apply within ~5 seconds, no restart
--label filter — expose only one database per Cursor project
--no-dynamic — block runtime mdb_connect for locked-down projects
Read-only by default — writes blocked unless readOnly: false

Two connection modes

Always call mdb_list_databases first — it tells the AI which mode applies.

Mode	When	How
A — Config label	DB defined in `config.json`	`mdb_query(database="analytics", query="...")`
B — Dynamic	User gives credentials in chat	`mdb_connect(...)` then omit `database` on other tools

See USAGE.md for full examples and AI workflow.

Quick Start

1. Install & build

cd multi-monetdb-mcp-server
npm install
npm run build

2. Add to Cursor

Global or project .cursor/mcp.json:

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": ["C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js"]
    }
  }
}

3. First use

Ask the AI to call mdb_list_databases. It will show config labels or guide you through mdb_connect.

Restricting access per project (Cursor)

When multiple environments exist (production, staging, dev), you can limit what the AI sees per Cursor project using .cursor/mcp.json in each project folder.

Option 1: `--label` (single database from shared config)

One global ~/.mcp-monetdb/config.json holds all environments. Each project exposes only its label:

~/.mcp-monetdb/config.json (shared):

{
  "connections": [
    { "label": "production", "host": "prod.db.com", "port": 50000, "user": "ro", "password": "...", "database": "warehouse", "readOnly": true },
    { "label": "staging",    "host": "stg.db.com",  "port": 50000, "user": "dev", "password": "...", "database": "warehouse", "readOnly": true },
    { "label": "local",      "host": "localhost",    "port": 50000, "user": "monetdb", "password": "monetdb", "database": "demo", "readOnly": false }
  ]
}

Project A — .cursor/mcp.json (production only):

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": [
        "C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js",
        "--label",
        "production"
      ]
    }
  }
}

Project B — .cursor/mcp.json (staging only):

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": [
        "C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js",
        "--label",
        "staging"
      ]
    }
  }
}

Effect:

mdb_list_databases shows only the filtered label
AI cannot see other environment names
AI uses database="production" (or "staging") on tool calls

Option 2: Project-specific config file

Each project has its own config with only the connections it needs:

Project A — .cursor/mcp.json:

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": [
        "C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js",
        "--config",
        "C:/Projects/ProjectA/.cursor/monetdb.json"
      ]
    }
  }
}

ProjectA/.cursor/monetdb.json:

{
  "connections": [
    {
      "label": "production",
      "host": "prod.db.com",
      "port": 50000,
      "user": "readonly",
      "password": "secret",
      "database": "warehouse",
      "readOnly": true
    }
  ]
}

Effect:

Other environments are not in the file at all
No --label needed — only one connection exists
Best for strongest isolation between teams/projects

Option 3: `--no-dynamic` (block runtime credentials)

Prevent the AI from calling mdb_connect with arbitrary credentials. Use with --label or a project config:

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": [
        "C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js",
        "--label",
        "production",
        "--no-dynamic"
      ]
    }
  }
}

Effect:

mdb_connect is rejected — config labels only
User cannot bypass restriction by pasting credentials in chat
Recommended for production-facing projects

Option 4: Combine all restrictions (recommended for production)

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": [
        "C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js",
        "--config",
        "C:/Projects/MyApp/.cursor/monetdb.json",
        "--label",
        "production",
        "--no-dynamic"
      ]
    }
  }
}

Restriction summary

Flag / setting	What it restricts
`--label <name>`	Only one config label visible to AI
`--config <path>`	Which config file to load (project-specific)
`--no-dynamic`	Blocks `mdb_connect` (runtime credentials)
`"readOnly": true`	Blocks INSERT/UPDATE/DELETE/DROP in SQL
`"enabled": false`	Hides a connection from shared config (soft disable)

Custom config via environment variable

Alternative to --config in args:

{
  "mcpServers": {
    "monetdb": {
      "command": "node",
      "args": ["C:/Code/MCPServer/multi-monetdb-mcp-server/dist/index.js", "--label", "staging"],
      "env": {
        "MCP_MONETDB_CONFIG": "C:/Projects/MyApp/.cursor/monetdb.json"
      }
    }
  }
}

Default config path: ~/.mcp-monetdb/config.json

Config file reference

{
  "connections": [
    {
      "label": "analytics",
      "host": "db.example.com",
      "port": 50000,
      "user": "readonly_user",
      "password": "secret",
      "database": "analytics",
      "enabled": true,
      "readOnly": true
    }
  ]
}

Field	Default	Description
`label`	(required)	Name used as `database` parameter in tool calls
`host`	—	MonetDB server hostname
`port`	`50000`	MAPI port
`user`	—	Username
`password`	`""`	Password
`database`	—	Database name
`url`	—	Full MAPI URL (alternative to host/user/password/database)
`enabled`	`true`	Set `false` to hide without removing
`readOnly`	`true`	Block write queries
`timeout`	`10000`	Connection timeout (ms)

Environment variable substitution in config values:

{ "password": "${MONETDB_PASSWORD:-monetdb}" }

Tools

Tool	Description
`mdb_list_databases`	Start here. Labels, session status, connection guide
`mdb_connect`	Runtime credentials (blocked when `--no-dynamic`)
`mdb_disconnect`	Close dynamic session
`mdb_query`	Execute SQL
`mdb_list_tables`	List tables
`mdb_describe_table`	Column types
`mdb_list_schemas`	List schemas
`mdb_health_check`	Connectivity check
`mdb_explain`	EXPLAIN plan

Security

Read-only by default (readOnly: true)
Use --no-dynamic + --label in production Cursor projects
Dynamic credentials never saved to config
Multi-statement queries rejected
Config passwords excluded from git via .gitignore

Source layout

src/
  index.ts                 Entry point
  types.ts                 Shared types
  config/                  CLI, schemas, loader
  connection/              Pool, dynamic session
  sql/                     Safety, query execution
  guidance/                AI connection guide
  tools/                   MCP tool registrations

License

Apache-2.0

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

dataOAuth
co.thinair
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
Databases Developer Tools
2
Draxlr AOAuth
com.draxlr.api
Draxlr's remote MCP server connects AI assistants to your SQL databases and dashboards. Explore schemas, run read-only queries, manage saved queries and dashboards, and export results, all with row-level security so each user sees only their own data.
Data Visualization Databases Search
151
QueryBearOAuth
io.github.spencerpauly
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
Databases RAG Systems
2
mcp AOAuth
co.axiom
List datasets, schemas, run APL queries, and use prompts for exploration, anomalies, and monitoring.
Databases Monitoring Search
29

Related MCP Servers

Common Database MCP Server
Databases Developer Tools
drainney-jrt
A
license
Not graded
quality
D
maintenance
Enables safe exploration and querying of multiple databases (PostgreSQL, MySQL, SQLite, DB2) with read-only defaults, connection pooling, and parameterized queries for SQL injection prevention.
Updated 6 months ago (2026-04-13 09:39 UTC)
1
MIT
mcp-postgres
Databases Developer Tools RAG Systems
Filipescordeiro2
F
license
Not graded
quality
D
maintenance
Enables AI agents to execute SQL queries and introspect PostgreSQL schemas, tables, and indexes with read-only safety by default. Supports optional write operations and works with Claude, LangChain, and other agents via stdio or HTTP transports.
Updated 6 months ago (2026-04-03 00:38 UTC)
-
mcp-mysql-client
Databases
gistrec
A
license
A
quality
B
maintenance
Provides AI agents a secure MCP interface to a single MySQL or MariaDB database, enabling schema inspection, read-only queries, query planning, and guarded write operations with strict safety controls.
Updated a month ago (2026-08-23 00:24 UTC)
6
23 npm
MIT
mcp-database-universal
Databases Developer Tools
kobramantra-debug
A
license
Not graded
quality
A
maintenance
Enables AI agents to safely explore and query databases across SQLite, PostgreSQL, MySQL, and MSSQL, with schema introspection, natural language queries, and data profiling.
Updated a month ago (2026-08-27 12:42 UTC)
MIT

multi-monetdb-mcp-server

Documentation

Features

Two connection modes

Quick Start

1. Install & build

2. Add to Cursor

3. First use

Restricting access per project (Cursor)

Option 1: --label (single database from shared config)

Option 2: Project-specific config file

Option 3: --no-dynamic (block runtime credentials)

Option 4: Combine all restrictions (recommended for production)

Restriction summary

Custom config via environment variable

Config file reference

Tools

Security

Source layout

License

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Common Database MCP Server

mcp-postgres

mcp-mysql-client

mcp-database-universal

Option 1: `--label` (single database from shared config)

Option 3: `--no-dynamic` (block runtime credentials)