mainframe-mcp-server
MCP server for IBM z/OS jobs, datasets, USS, and operational diagnostics via Zowe SDK.
Package Details
@notharshhaa/mainframe-mcp-server
Environment Variables
z/OSMF hostname or IP address
z/OSMF HTTPS port (default 443)
Optional API gateway or mediation layer prefix for z/OSMF
z/OS user id (required with ZOSMF_PASSWORD unless ZOSMF_TOKEN is set)
Password for basic auth (required with ZOSMF_USER unless ZOSMF_TOKEN is set)
Auth token (alternative to user/password)
Token type when using ZOSMF_TOKEN (e.g. LTPA2)
Verify TLS certificates (true in production)
Log level: fatal, error, warn, info, debug, trace, silent
Transport: stdio (IDE) or sse (container/network)
Listen port when MCP_TRANSPORT=sse
Max lines returned from a single spool DD
Max lines returned from dataset or USS reads
Max spool files fetched during diagnostics
Max RACF audit log lines per query
CICSplex name or region APPLID (required for CICS tools)
CMCI hostname (defaults to ZOSMF_HOST)
CMCI HTTPS port (default 1490)
CMCI REST base path
Db2 subsystem location name (required for Db2 tools)
Db2 REST hostname (defaults to ZOSMF_HOST)
Db2 REST port (default 50400)
Db2 REST base path
Optional SMF summary dataset for offline metrics
Query z/OSMF RMF metrics when available
USS path to RACF audit log file
Sequential dataset containing RACF audit records
When true, blocks write tools such as submit_jcl
Comma-separated allowlist of MCP tool names
Comma-separated blocklist of MCP tool names
Comma-separated dataset patterns (e.g. USERDEV.*,SYS1.*)
Comma-separated USS path prefixes
Log every tool invocation to stderr (SIEM-friendly JSON)
Maximum inline JCL size for submit_jcl