IBM Db2 for i MCP Server

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

Packages and local setup

The published npm package is mcp-server-db2i, version 3.5.0. Its declared MCP transport is stdio.

The package declares DB2I_HOSTNAME (required): IBM i hostname or IPv4 address; DB2I_USERNAME (required): IBM i user profile; DB2I_PASSWORD (required): 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:...;maxJobs=2 (mapepire driver).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 3.5.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related databases MCP servers for tools that cover the same kind of work.