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

elsewhere-mcp

v0.1.0

Published

Elsewhere as MCP tools — give any agent the ability to build in a persistent shared 3D world.

Readme

Elsewhere MCP server

Give any AI agent the ability to build in a persistent shared world.

Elsewhere is a protocol, not an app, and this is how an agent speaks it. Point Claude Code, Cursor, or anything else that speaks MCP at your Elsewhere account and it can find space, claim it, and build — through the same public endpoints and the same validator a stranger's HTTP request would hit.

Set up

  1. Sign in to Elsewhere, open Developer API, and create a key. Tick the scopes the agent actually needs. read and build is the usual pair; add claim if it should be able to take new space for you. Leave transfer off unless you genuinely want it able to give your regions away.

  2. Add it to your MCP config.

    Claude Code — ~/.claude.json (or .mcp.json in a project):

    {
      "mcpServers": {
        "elsewhere": {
          "command": "npx",
          "args": ["-y", "elsewhere-mcp"],
          "env": {
            "ELSEWHERE_API_KEY": "sw_live_...",
            "ELSEWHERE_API_URL": "https://elsewhere-api.onrender.com"
          }
        }
      }
    }
  3. Ask for something.

    Find me somewhere quiet for an observatory, claim it, and build one.

Tools

| Tool | What it does | | --- | --- | | world_info | How big the world is, how much is claimed, the current version | | find_space | Search for unclaimed space matching a description, with reasoning | | check_space | Ask whether one exact volume is free, and what it overlaps if not | | describe_region | Owner, contents, size, and whether you may build there | | my_regions | What this key's account holds | | claim_region | Take unclaimed space. Free. Needs the claim scope | | build | Create, update and delete objects. The main one | | register_asset | Reference an external 3D file by content hash. Needs assets | | credits | Hosted-AI balance. Nothing these tools do spends it |

Two things worth knowing

Coordinates inside a region are region-local. 0, 0, 0 is the centre of your region at ground level, whatever its position in the world. Objects are positioned by their centre, so a 4m wall standing on the ground sits at y=2. This is not a quirk — it is what will keep the world free of floating-point drift when regions stop being twenty metres across.

Your tokens are yours. These tools cost nothing. When Claude Code drives Elsewhere, the model tokens are billed by your own provider on your own plan; Elsewhere only ever charges for its own hosted AI Builder, which is a different thing you did not use. The credits tool exists so an agent can say so accurately rather than guessing.

Running against your own world

ELSEWHERE_API_URL=http://127.0.0.1:4000 \
ELSEWHERE_API_KEY=sw_live_... \
npx elsewhere-mcp

Anything written to stdout that is not an MCP frame corrupts the session, so errors go to stderr. If the server exits immediately, that is where the reason is.