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

mcpops

v0.1.0

Published

Universal MCP operations CLI — manage any MCP gateway from one control plane

Downloads

91

Readme

mcpops

Universal MCP operations CLI — manage any MCP gateway from one control plane.

mcpops is the Terraform of the MCP ecosystem. Instead of building another gateway, it manages them all through a provider-agnostic plugin architecture.

mcpops status                              # unified status across all backends
mcpops tools list                          # discover tools across all instances
mcpops connect factory edge --mode bridge  # federate between gateways
mcpops discover factory mqtt               # discover IoT devices

Why mcpops

The MCP gateway space is crowded — MetaMCP, Microsoft MCP Gateway, mcp-iot-gateway, and dozens more. Each has its own CLI, API, and management model. mcpops unifies them behind a single control plane.

  • Provider-agnostic: One CLI for all your MCP infrastructure
  • Config-as-code: YAML config for your entire MCP topology
  • Federation: Connect instances across providers (peer or bridge mode)
  • Discovery: Find tools and devices across all backends
  • Extensible: Add new providers with a simple TypeScript interface

Install

npm install -g mcpops

Or run directly:

npx mcpops --help

Quick Start

1. Add your gateways

# Add an IoT gateway
mcpops provider add iot-gateway factory http://192.168.1.100:45678/mcp \
  --auth-type api-key --auth-key igt_xxxx

# Add a MetaMCP instance
mcpops provider add metamcp staging http://localhost:12008 \
  --auth-type api-key --auth-key sk_mt_xxxx

2. Check status

mcpops status
mcpops status

INSTANCE  PROVIDER     STATUS       TOOLS     PEERS
──────────────────────────────────────────────────────
factory   iot-gateway  ● connected  42 tools  3 peers
staging   metamcp      ● connected  18 tools  5 peers

3. Discover tools

mcpops tools list
mcpops tools list --instance factory
mcpops tools call factory iot_discover '{"connection":"mqtt"}'

4. Federate instances

mcpops connect factory staging --mode bridge --live

5. Discover devices

mcpops discover factory mqtt

Commands

| Command | Description | |---------|-------------| | mcpops status [instance] | Unified status across all instances | | mcpops provider list | List providers and configured instances | | mcpops provider add <provider> <name> <url> | Add a gateway instance | | mcpops provider remove <name> | Remove an instance | | mcpops tools list [-i instance] | List tools across instances | | mcpops tools call <instance> <tool> [args] | Call a tool | | mcpops connect <from> <to> [--mode] | Federate two instances | | mcpops disconnect <from> <to> | Remove federation | | mcpops discover <instance> [scope] | Discover devices/services | | mcpops config show | Display configuration | | mcpops config export | Export config as YAML | | mcpops config validate | Validate config file |

Configuration

Config lives at ~/.config/mcpops/config.yaml:

version: 1
instances:
  factory:
    provider: iot-gateway
    url: http://192.168.1.100:45678/mcp
    auth:
      type: api-key
      key: igt_xxxx
  staging:
    provider: metamcp
    url: http://localhost:12008
    auth:
      type: api-key
      key: sk_mt_xxxx

federations:
  - from: factory
    to: staging
    mode: bridge

Override the config path:

MCPOPS_CONFIG=./my-config.yaml mcpops status

Providers

Built-in

| Provider | Description | Federation | Discovery | |----------|-------------|------------|-----------| | iot-gateway | mcp-iot-gateway | ✅ peer + bridge | ✅ IoT devices | | metamcp | MetaMCP aggregator | — | — |

Writing a Provider

Implement the Provider abstract class:

import { Provider } from "mcpops";

export class MyGatewayProvider extends Provider {
  readonly name = "my-gateway";
  readonly version = "1.0.0";
  readonly capabilities = {
    canFederate: false,
    canBridge: false,
    canDiscover: false,
    supportsAuth: true,
    supportsNamespaces: false,
  };

  async connect(config) { /* ... */ }
  async disconnect(instanceId) { /* ... */ }
  async healthCheck(instanceId) { /* ... */ }
  async status(instanceId) { /* ... */ }
  listInstances() { /* ... */ }
  async listTools(instanceId) { /* ... */ }
  async callTool(instanceId, tool, args) { /* ... */ }
  async shutdown() { /* ... */ }
}

License

MIT — Symbia Labs