# @ibm/ibmi-mcp-server [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/IBM/ibmi-mcp-server  
**GitHub Stars:** 87  
**npm Downloads (last month):** 3162  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ibm-ibmi-mcp-server

## Description
MCP server for  IBM i systems

## Tools
Capabilities this server exposes over MCP:

- **Database** — Tables, indexes, constraints, statistics

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ibmi-mcp-server": {
    "command": "npx",
    "args": ["-y","@ibm/ibmi-mcp-server@latest"],
    "env": {
      "DB2I_HOST": "",
      "DB2I_USER": "",
      "DB2I_PASS": "",
      "DB2I_PORT": "",
      "DB2I_IGNORE_UNAUTHORIZED": "",
      "MCP_SERVER_CONFIG": ""
    }
  }
}
```

**Requires environment variables:** `DB2I_HOST`, `DB2I_USER`, `DB2I_PASS`, `DB2I_PORT`, `DB2I_IGNORE_UNAUTHORIZED`, `MCP_SERVER_CONFIG` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What @ibm/ibmi-mcp-server MCP server does

The @ibm/ibmi-mcp-server MCP server gives AI agents an MCP interface to IBM i systems. Its tool engine uses YAML files to define SQL statements, parameters, descriptions, and tool groupings. Agents can use those definitions to query Db2 for i, inspect system information, monitor performance, and perform supported database operations.

The repository also includes a separate `ibmi` command-line package. That CLI shares the YAML SQL tool engine, but it is intended for terminal use, scripts, local exploration, and CI/CD rather than MCP client connections.

## How it works

An MCP client sends a tool request to the server. The server resolves the selected YAML-defined tool, connects to IBM i through Mapepire, executes the associated SQL, and returns the result to the agent. Mapepire must be running on the IBM i system; the quick-start configuration uses port 8076.

Tool definitions can be supplied from the repository’s included tool files or from custom YAML files. The example configuration includes a performance toolset with system status, memory pool, and active job monitoring. A custom definition can point at an IBM i source and contain its own SQL statement and parameters.

The server supports `stdio` and HTTP transport modes. The HTTP quick start exposes a health endpoint at `/healthz` and an MCP endpoint at `/mcp`, which can be used to check availability and list tools.

## Setup and configuration

Running the @ibm/ibmi-mcp-server MCP server requires Node.js 18 or newer and a reachable Mapepire instance on IBM i. Configure the connection with environment variables for the IBM i host, user, password, port, and certificate behavior:

- `DB2i_HOST`
- `DB2i_USER`
- `DB2i_PASS`
- `DB2i_PORT`
- `DB2i_IGNORE_UNAUTHORIZED`

A typical launch uses `npx` with the server package, an HTTP transport flag, and a path to a YAML tool file. Docker is also supported; the documented container example mounts the tools directory and environment file, sets `MCP_SERVER_CONFIG`, and publishes port 3010.

## Tools and capabilities

- Execute YAML-defined SQL tools against Db2 for i.
- Create custom tools by associating SQL statements with named sources and parameters.
- Group tools into toolsets for selective loading.
- Monitor IBM i performance through the documented example tools.
- Serve MCP requests over stdio or HTTP.
- Expose health and tool-listing endpoints when using the HTTP setup.
- Use the related `ibmi` CLI with the same tool definitions when an MCP server is unnecessary.

_Full upstream README: https://allmcps.com/mcp/ibm-ibmi-mcp-server/readme_