Home › Development › IBM Db2 for i

IBM Db2 for i

Read-only SQL queries and schema inspection for IBM Db2 for i over ODBC, JT400 or Mapepire (SSH).

TypeScript

★ 29 stars Last pushed 2026-11-11 License: MIT

View repository → Website →

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Package (npm 3.8.7)

npx -y [email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "DB2I_HOSTNAME": "<YOUR_VALUE>",
        "DB2I_USERNAME": "<YOUR_VALUE>",
        "DB2I_PASSWORD": "<YOUR_VALUE>"
      }
    }
  }
}

DB2I_HOSTNAME required — IBM i hostname or IPv4 address
DB2I_USERNAME required — IBM i user profile
DB2I_PASSWORD required secret — IBM i password
DB2I_SCHEMA — Default schema (library)
DB2I_PROFILES — Path to a YAML file of IBM i systems. When set, it replaces the DB2I_* connection variables
QUERY_ALLOWED_SCHEMAS — Comma-separated schemas the server may read. Empty disables the check.
DB2I_DRIVER — Database driver: odbc (default, IBM i Access ODBC driver, no Java), jt400 (install node-jt400 next to the server; needs a JDK at install and a JRE at runtime) or mapepire (install @ibm/mapepire-js and ssh2; Mapepire over SSH, needs Java on the IBM i only)
DB2I_JDBC_OPTIONS — Extra JT400 JDBC properties, semicolon-separated (jt400 and mapepire drivers)
DB2I_ODBC_OPTIONS — Extra IBM i Access ODBC connection keywords, semicolon-separated (odbc driver)
DB2I_MAPEPIRE_OPTIONS — SSH and Mapepire settings, semicolon-separated, e.g. hostKey=SHA256:...;agent=true;maxJobs=2 (mapepire driver)