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

@multiplayer-app/cli

v2.0.59

Published

Multiplayer CLI

Downloads

5,109

Readme

@multiplayer-app/cli

AI-powered debugging agent and release management CLI for Multiplayer.

Install

npm install -g @multiplayer-app/cli

Supports macOS (arm64, x64), Linux (arm64, x64), and Windows (arm64, x64). The correct platform binary is installed automatically.

Commands

| Command | Description | |---------|-------------| | multiplayer [agent] | Start the debugging agent (default) | | multiplayer releases create | Register a release | | multiplayer deployments create | Register a deployment | | multiplayer sourcemaps upload | Upload sourcemap files | | multiplayer auth login | Log in via browser OAuth | | multiplayer auth logout | Log out and clear credentials | | multiplayer auth status | Check authentication status | | multiplayer mcp | Start an MCP server for AI agent integration |


Debugging Agent

Connects to the Multiplayer backend and automatically resolves incoming issues using AI.

multiplayer [agent] [options]

Options are resolved in this order: CLI flag → environment variable → config profile.

| Flag | Env var | Description | |------|---------|-------------| | --api-key <key> | MULTIPLAYER_API_KEY | Multiplayer API key | | --dir <path> | MULTIPLAYER_DIR | Project directory (must be a git repo) | | --model <name> | AI_MODEL | AI model (e.g. claude-sonnet-4-6, gpt-4o) | | --model-key <key> | AI_API_KEY | AI provider API key (not required for Claude models) | | --model-url <url> | AI_BASE_URL | Base URL for OpenAI-compatible APIs | | --headless | MULTIPLAYER_HEADLESS=true | Run without TUI — outputs structured JSON logs | | --profile <name> | MULTIPLAYER_PROFILE | Config profile to load (default: default) | | --name <name> | MULTIPLAYER_AGENT_NAME | Agent name (defaults to hostname) | | --max-concurrent <n> | MULTIPLAYER_MAX_CONCURRENT | Max issues resolved in parallel (default: 2) | | --no-git-branch | MULTIPLAYER_NO_GIT_BRANCH=true | Work in current branch — no worktree, no push | | --health-port <port> | MULTIPLAYER_HEALTH_PORT | HTTP health check port (headless mode only) | | --url <url> | MULTIPLAYER_URL | Multiplayer API base URL |

TUI mode (default)

An interactive terminal dashboard that shows active sessions and live logs.

multiplayer --api-key <key> --dir /path/to/repo --model claude-sonnet-4-6

Headless mode

Outputs newline-delimited JSON logs — suitable for CI, containers, and log aggregators.

multiplayer --headless --api-key <key> --dir /path/to/repo --model claude-sonnet-4-6

In headless mode, SIGTERM waits for active sessions to finish before exiting; SIGINT exits immediately.

Config profiles

Create a .multiplayer/config file in your project directory or home directory (~/.multiplayer/config). Uses INI format — the same as AWS credentials.

[default]
api_key        = <your-api-key>
dir            = /path/to/repo
model          = claude-sonnet-4-6
max_concurrent = 2

[staging]
api_key        = <staging-api-key>
dir            = /path/to/staging-repo
model          = gpt-4o
model_key      = <openai-api-key>

All supported profile keys:

| Key | Description | |-----|-------------| | api_key | Multiplayer API key | | dir | Project directory | | model | AI model name | | model_key | AI provider API key | | model_url | Base URL for OpenAI-compatible APIs | | name | Agent name | | url | Multiplayer API base URL | | max_concurrent | Max parallel issues | | no_git_branch | true to skip branch/worktree creation |


Auth

multiplayer auth login    # Log in via browser OAuth flow
multiplayer auth logout   # Log out and clear stored credentials
multiplayer auth status   # Check current authentication status

Releases

multiplayer releases create [options]

| Flag | Env var | Description | |------|---------|-------------| | --api-key <key> | MULTIPLAYER_API_KEY | Multiplayer API key | | --service <name> | SERVICE_NAME | Service name | | --release-version <version> | RELEASE | Release version | | --commit-hash <hash> | COMMIT_HASH | Commit hash | | --repository-url <url> | REPOSITORY_URL | Repository URL | | --release-notes <notes> | RELEASE_NOTES | Release notes (optional) | | --base-url <url> | BASE_URL | API base URL (optional) |

Example:

multiplayer releases create \
  --api-key $MULTIPLAYER_API_KEY \
  --service my-service \
  --release-version 1.2.3 \
  --commit-hash abc123 \
  --repository-url https://github.com/org/repo

Deployments

multiplayer deployments create [options]

| Flag | Env var | Description | |------|---------|-------------| | --api-key <key> | MULTIPLAYER_API_KEY | Multiplayer API key | | --service <name> | SERVICE_NAME | Service name | | --release <version> | RELEASE | Release version | | --environment <name> | ENVIRONMENT | Environment name | | --base-url <url> | BASE_URL | API base URL (optional) |

Example:

multiplayer deployments create \
  --api-key $MULTIPLAYER_API_KEY \
  --service my-service \
  --release 1.2.3 \
  --environment production

Sourcemaps

multiplayer sourcemaps upload <directories...> [options]

| Flag | Env var | Description | |------|---------|-------------| | --api-key <key> | MULTIPLAYER_API_KEY | Multiplayer API key | | --service <name> | SERVICE_NAME | Service name | | --release <version> | RELEASE | Release version | | --base-url <url> | BASE_URL | API base URL (optional) |

Example:

multiplayer sourcemaps upload ./dist ./build \
  --api-key $MULTIPLAYER_API_KEY \
  --service my-service \
  --release 1.2.3

MCP Server

multiplayer mcp starts an MCP server over stdio, exposing Multiplayer operations as tools that AI agents (Claude Desktop, Claude Code, Cursor, etc.) can call directly.

Tools

| Tool | Description | |------|-------------| | create_release | Register a release for a service | | create_deployment | Deploy a release to an environment | | upload_sourcemaps | Upload .map files from local directories |

Setup

Add the server to your MCP client config. Example for Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "multiplayer": {
      "command": "multiplayer",
      "args": ["mcp"],
      "env": {
        "MULTIPLAYER_API_KEY": "<your-api-key>"
      }
    }
  }
}

Example for Claude Code (~/.claude/mcp.json):

{
  "mcpServers": {
    "multiplayer": {
      "command": "multiplayer",
      "args": ["mcp"],
      "env": {
        "MULTIPLAYER_API_KEY": "<your-api-key>"
      }
    }
  }
}

Once configured, the AI can create releases, deployments, and upload sourcemaps without any shell commands or manual steps.