IBM Db2 for i runs on your own machine — the client starts it, so there is no endpoint to ping. 539 installs a week from npm. Last commit 6 Nov 2026.
Read-only SQL queries and schema inspection for IBM Db2 for i over ODBC, JT400 or Mapepire (SSH).
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
ENV DB2I_PASSWORD=""
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-server-db2i -e 'DB2I_HOSTNAME=<DB2I_HOSTNAME>' -e 'DB2I_USERNAME=<DB2I_USERNAME>' -e 'DB2I_PASSWORD=<DB2I_PASSWORD>' -- npx -y mcp-server-db2i
{
"mcpServers": {
"mcp-server-db2i": {
"command": "npx",
"args": [
"-y",
"mcp-server-db2i"
],
"env": {
"DB2I_HOSTNAME": "<DB2I_HOSTNAME>",
"DB2I_PASSWORD": "<DB2I_PASSWORD>",
"DB2I_USERNAME": "<DB2I_USERNAME>"
}
}
}
}
[mcp_servers.mcp-server-db2i]
command = "npx"
args = ["-y", "mcp-server-db2i"]
env = { DB2I_HOSTNAME = "<DB2I_HOSTNAME>", DB2I_USERNAME = "<DB2I_USERNAME>", DB2I_PASSWORD = "<DB2I_PASSWORD>" }
{
"mcpServers": {
"mcp-server-db2i": {
"command": "npx",
"args": [
"-y",
"mcp-server-db2i"
],
"env": {
"DB2I_HOSTNAME": "<DB2I_HOSTNAME>",
"DB2I_PASSWORD": "<DB2I_PASSWORD>",
"DB2I_USERNAME": "<DB2I_USERNAME>"
}
}
}
}
{
"servers": {
"mcp-server-db2i": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-db2i"
],
"env": {
"DB2I_HOSTNAME": "<DB2I_HOSTNAME>",
"DB2I_PASSWORD": "<DB2I_PASSWORD>",
"DB2I_USERNAME": "<DB2I_USERNAME>"
}
}
}
}
Put your own values in place of
<DB2I_HOSTNAME> (IBM i hostname or IPv4 address), <DB2I_USERNAME> (IBM i user profile), <DB2I_PASSWORD> (IBM i password).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
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)).
MCP server for SQL Server: schema inspection, safe read-only queries, query plan analysis
Read-only SQL Server introspection and querying: schema, definitions, dependencies and data.
MCP server for SAP SQL Anywhere 17: explore schemas and run read-only queries.
MCP server for one MySQL database: schema, read-only queries and guarded writes.
Read-only SQL querying + schema introspection over Postgres & SQLite, with a gated write mode.
Explore and query PostgreSQL read-only: catalogue search, schema introspection and bounded queries.
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
Database admin MCP: schema inspection, query optimization for PostgreSQL and MySQL
Answers built from our own checks of this server.