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

@evolvablegamer/sts2-mcp

v0.1.1

Published

The MCP server runs inside the game MOD; no DSH, Node or Python gameplay proxy is required. The game is not included. Approved target: macOS arm64, Steam build `23811903`, MOD source [150d80d](https://github.com/EvolvableGamer/STS2-Agent/tree/150d80d0efe4

Readme

Slay the Spire 2 official gameplay MCP kit

The MCP server runs inside the game MOD; no DSH, Node or Python gameplay proxy is required. The game is not included. Approved target: macOS arm64, Steam build 23811903, MOD source 150d80d. Windows has no approved payload yet.

These lifecycle prompts require installer 0.1.1 or newer. The old 0.1.0 CLI has no update command; if your registry does not yet offer a supporting version, wait for the maintainer to publish it. Install the game and Node.js 22+ first. Your Harness needs local terminal access and permission to configure MCP. You do not need to install a DSH plugin or management MCP before using the default path.

Default: one installation prompt

Copy this into your Agent:

Install the official Slay the Spire 2 MCP kit with the game closed. First identify this Harness. If the sandbox blocks the command, request its normal one-shot write approval; do not use sudo or chown. In DSH, inspect only DSH_PROFILE_DIR/DSH_PROFILE and verify the active profile; do not dump the environment or guess paths. If missing, stop and ask me to use the correct DSH terminal. Then run npx -y @evolvablegamer/sts2-installer@latest dsh-setup; it deploys the MOD and registers the current profile automatically, without a separate DSH installer plugin or hand-written mcpServers. For another local Harness, run npx -y @evolvablegamer/sts2-installer@latest install --kit mcp, then merge its gameplay MCP entry sts2 using Streamable HTTP at http://127.0.0.1:19080/mcp. Preserve other config and inspect an existing entry. Report reconnect/restart needs. I will open the game and personally confirm Enable Mods; do not bypass it. Read get_game_state once connected and wait for me to ask you to play; do not resume a personal save automatically.

In DSH, dsh-setup is the same unified CLI's profile-registration branch, not a separate plugin or mcpServers config file. Its CLI must be available on PATH. The installer verifies and deploys files; the Agent uses its Host's configuration format to register/reconnect MCP. mcp.json describes the connection and must not replace the Host's complete config. One prompt starts the workflow; necessary approvals, restarts and your personal Enable Mods confirmation still apply.

Once connected, say 开始玩杀戮尖塔 2。. Your original Agent uses the gameplay tools, without a persona/mode/compression replacement or sts2_play helper.

Default: update prompt

For an installation made through the CLI above:

Update the Slay the Spire 2 kit with the game closed. Identify the original installation route, not just the current Harness: a DSH terminal dsh-setup installation uses npx -y @evolvablegamer/sts2-installer@latest dsh-update in the same verified profile; a generic CLI installation uses npx -y @evolvablegamer/sts2-installer@latest update --kit mcp; the optional native DSH plugin uses sts2_update after updating/reloading that entry. If route/profile ownership is unclear, stop and report it. Use the locked compatible package set, preserve other config and backups, and report file changes, game startup and Host reconnection separately.

Only the installer entry needs updating. Updates preserve rollback snapshots and the original uninstall baseline; unavailable or uninstalled kits are not silently added. Modified files are refused unless explicitly approved for backed-up force restoration.

Default: uninstall prompt

Uninstall the official Slay the Spire 2 MCP kit with the game closed. Identify the original route: DSH terminal dsh-setup installations use npx -y @evolvablegamer/sts2-installer@latest dsh-remove in the same verified profile to restore MODs and registration together; generic CLI installations use npx -y @evolvablegamer/sts2-installer@latest uninstall --kit mcp, then remove only the sts2 registration added by this installation; optional native DSH installations use sts2_uninstall. Preserve other services and files. If route/profile/registration ownership is unclear, keep it and tell me instead of guessing. Report file and registration restoration separately.

The generic CLI does not silently edit arbitrary Harness configuration. Removing an npm package or MCP registration alone does not uninstall the MOD. If you chose a DSH-specific installation route, use its matching update/uninstall route so registration receipts are also restored.

Optional: DSH native integration

Add @evolvablegamer/sts2-installer on the Plugins page, then say 安装杀戮尖塔 in an ordinary conversation. This optional adapter is in the same installer package, not a fourth public package or a prerequisite for the CLI.

It provides five management tools and manages DSH's gameplay MCP registration. After updating/reloading the installer plugin, say 更新杀戮尖塔套件 to use sts2_update; close the game and use sts2_uninstall before removing the installer plugin. Older DSH versions may require restart; use the returned status. Existing terminal-profile installations retain dsh-update and dsh-remove.

Optional: management MCP

For a local Harness without terminal tools, or users who prefer explicit lifecycle tools, register this stdio connection once using your Host's config format:

{"serverName":"sts2-manager","transport":"stdio","command":"npx","args":["-y","@evolvablegamer/sts2-installer@latest","mcp"]}

It exposes sts2_install, sts2_update, sts2_uninstall, sts2_diagnose and sts2_launch outside the game. Gameplay remains on the separate sts2 server. Restart the manager after updating its entry to load a new release lock. Bridge reachability does not prove your Host reconnected; a remote-only Harness unable to run local processes cannot directly deploy files on your gaming computer.

There are three public package targets: @evolvablegamer/sts2-competition (independent competition MOD), this gameplay MCP package, and @evolvablegamer/sts2-installer. Competition artifacts and approved installation handling are awaiting handoff, so --kit competition remains unavailable. Entrants with their own gameplay MCP do not need this official kit.

Contents and licenses

The package contains the MOD ZIP, release metadata, mcp.json, eight default tool names, and a legacy-compatible optional DSH connection patch. Full/raw gameplay access remains explicit. It contains no competition workflow, scoring, recorder or saves. The installer is not a gameplay runtime dependency.

Configuration and documentation are MIT-licensed; the bundled MOD is AGPL-3.0-only. See assets/MOD_LICENSE, assets/MOD_SOURCE.json, and the ZIP's LICENSE/SOURCE.json for corresponding-source links and notices; retain them when redistributing.

Full installation, update and removal guide. Cross-Harness lifecycle support is distinct from on-device acceptance in each Harness; see the repository verification records for tested limits.