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

@zenstackhq/studio-mcp-remote

v1.1.0

Published

Local stdio MCP server bridging client calls and ZenStack local database proxy

Readme

@zenstackhq/studio-mcp-remote

@zenstackhq/studio-mcp-remote is a local stdio MCP server proxy designed for ZenStack Studio.

Problem

The hosted ZenStack Studio MCP server interacts with a user's database via a ZenStack proxy. When that proxy runs locally (e.g. http://localhost:2311), the hosted remote server cannot directly connect to it. @zenstackhq/studio-mcp-remote bridges this gap: it runs locally as a stdio MCP server (for Claude Desktop, Cursor, etc.), forwarding schema and check tool requests to the remote Studio MCP server while intercepting execute database tool requests locally to call the localhost proxy.

Installation & Usage

You can run @zenstackhq/studio-mcp-remote directly with npx or pnpm dlx:

npx -y @zenstackhq/studio-mcp-remote --remote <studio-mcp-url> --proxy <local-proxy-url> --authorization <authorization-token>

CLI Options

  • --remote, -r (Required): The URL of the remote ZenStack Studio MCP server.
  • --proxy, -p (Required): The URL of your local database proxy (e.g. http://localhost:2311).
  • --authorization, -a (Required): The base64-encoded UserClaim authorization token.

If any required flag is omitted, the CLI prints usage instructions and exits with status code 1.


MCP Client Configuration

Claude Desktop (claude_desktop_config.json)

Add @zenstackhq/studio-mcp-remote to your Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "zenstack": {
      "command": "npx",
      "args": [
        "-y",
        "@zenstackhq/studio-mcp-remote",
        "--remote",
        "https://studio.zenstack.dev/api/mcp/YOUR_PROJECT_REF",
        "--proxy",
        "http://localhost:2311",
        "--authorization",
        "eyJ0eXBlIjoic3VwZXJVc2VyIn0="
      ]
    }
  }
}

Cursor / VS Code MCP Configuration

{
  "mcpServers": {
    "zenstack": {
      "command": "npx",
      "args": [
        "-y",
        "@zenstackhq/studio-mcp-remote",
        "--remote",
        "https://studio.zenstack.dev/api/mcp/YOUR_MCP_REF",
        "--proxy",
        "http://localhost:2311",
        "--authorization",
        "eyJ0eXBlIjoic3VwZXJVc2VyIn0="
      ]
    }
  }
}

Generating the Authorization Token

The --authorization token is a base64-encoded JSON payload matching the UserClaim type:

export type UserClaim = { type: 'superUser' } | { type: 'user'; data: Record<string, unknown> }

SuperUser Claim Example (bash)

echo -n '{"type":"superUser"}' | base64
# Output: eyJ0eXBlIjoic3VwZXJVc2VyIn0=

Regular User Claim Example (bash)

echo -n '{"type":"user","data":{"id":"user-123","role":"ADMIN"}}' | base64
# Output: eyJ0eXBlIjoidXNlciIsImRhdGEiOnsiaWQiOiJ1c2VyLTEyMyIsInJvbGUiOiJBRE1JTiJ9fQ==

Development

# Install dependencies using pnpm
pnpm install

# Build
pnpm run build

# Run tests
pnpm test

License

MIT