npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

mcp-for-i

v0.1.11

Published

Local MCP server and control plane for IBM i workflows

Downloads

837

Readme

MCP-for-i

mcp-for-i is a local MCP server + control plane for IBM i workflows. It provides secure connection onboarding, keychain-backed credentials, runtime update controls, and IBM i tools for agent-driven operations.

Install

Install globally from npm:

npm i -g mcp-for-i

Verify commands:

mcp-for-i --help
mcp-for-i-control help

Quick Start

  1. Start the local control plane:
mcp-for-i-control serve
  1. Open the UI at:
http://127.0.0.1:3980
  1. Add IBM i connection profiles in the UI. Passwords are stored in the OS keychain, not plain config.

Background Startup (Windows)

Enable startup at login:

mcp-for-i-control setup

Check status:

mcp-for-i-control status

Disable startup:

mcp-for-i-control remove

Update and Version Management

Update to latest globally:

npm i -g mcp-for-i@latest

Install a specific version:

npm i -g [email protected]

Rollback example:

npm i -g [email protected]

Check current installed version:

mcp-for-i --version

Control Plane Runtime Actions

In the UI, runtime buttons behave as follows:

  • Install/Repair MCP
    • If running from a git checkout: runs local dependency repair/build.
    • If running as npm-installed package: runs global npm install/repair for latest package.
  • Update MCP
    • If running from a git checkout: pulls latest changes from origin/<current-branch>, then installs/builds.
    • If running as npm-installed package: upgrades global npm package to latest.
    • On Windows global installs, update runs in a detached updater and briefly restarts control plane to avoid file-lock (EBUSY) errors.
  • Update Skills
    • Pulls/clones the configured skills repository and branch into the local skills directory.

Development (Git Checkout)

For contributors working from source:

npm install
npm run build
npm test
npm run start:controlplane

Automated Release (No Manual Version Bump)

Use the release script instead of raw npm publish.

Patch release:

npm run release:patch

Minor release:

npm run release:minor

Major release:

npm run release:major

What it does:

  • Verifies git working tree is clean.
  • Runs npm test (unless --skip-tests is passed).
  • Checks npm published version.
  • Auto-bumps version only when local version is not ahead.
  • Publishes to npm.
  • Pushes commit/tag to GitHub.

Optional flags:

npm run release:patch -- --skip-tests
npm run release:patch -- --otp=123456
npm run release:patch -- --no-push

Security Model

  • Credential-bearing direct tool arguments are blocked for connection creation/update flows.
  • Passwords are stored in keychain when available.
  • Control plane is local-first (127.0.0.1 by default).
  • Guarded policy profile is the default for operational safety.
  • Tool schemas are strict (additionalProperties: false) with runtime argument validation, including nested connection/action/filter/profile payloads.
  • QSYS object names and source settings are validated before command execution to reduce interpolation and injection risk.

Links