mcp -db2i

This MCP server provides read-only access to IBM DB2 for i data via the Model Context Protocol. It supports two transports: stdio for AI clients running locally (e.g., Claude or Cursor IDE) and HTTP via a REST API for web or agent integrations. The available tools include querying data, inspecting schemas, listing tables and views, and retrieving metadata such as column details and constraints. Credentials are kept secure by using environment variables, and all queries are restricted to read-only operations to safeguard the underlying DB2i instance. To connect, configure a client with the db2i MCP server entry and point it to the npx-based invocation, ensuring your IBM i credentials are supplied through environment variables.

Examples of typical interactions include listing schemas, describing a table, listing indexes, and running a safe SELECT query against public views. The tools provided enable practical AI-assisted database exploration and answer generation without exposing write capabilities.

Prerequisites:

• Node.js 20.6 or higher
• npm (comes with Node.js)
• Access to an IBM i (DB2 for i) database

Installation steps:

1. Install the MCP server globally via npm:

npm install -g mcp-server-db2i

2. Prepare environment variables for DB2i access (example in a .env file):

DB2I_HOSTNAME=your-ibm-i-host.com
DB2I_USERNAME=your-username
DB2I_PASSWORD=your-password
DB2I_SCHEMA=your-default-schema  # optional

3. Run the MCP server using npx (as the default configuration expects):

# This will invoke the MCP server via npx as configured in mcp_config
# You can also run directly if you prefer:
npx mcp-server-db2i

4. Optional: Build and run via Docker (Dockerfile provided in the project):

docker build -t mcp-server-db2i .
docker run -e DB2I_HOSTNAME=... -e DB2I_USERNAME=... -e DB2I_PASSWORD=... -e DB2I_SCHEMA=... -p 8080:8080 mcp-server-db2i

5. Verify installation by requesting the server status or listing available tools via your MCP client or HTTP API.

Tips:

• Credentials must be supplied through environment variables; avoid hard-coding them in config files.
• The server enforces read-only queries for safety; attempting non-SELECT statements will be rejected.
• If using the HTTP transport, ensure token authentication is configured as described in the documentation.
• For Docker users, you can leverage the provided dockerfile and builder commands to containerize the server.
• The DB2I_SCHEMA variable is optional; if omitted, the server may default to a standard schema in your environment.
• Compatible clients include Cursor, Claude Desktop, Claude Code, and other MCP-enabled agents capable of stdio or REST communication.