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

studio-mcp

v0.0.20

Published

Make any CLI command an MCP server

Readme

Studio MCP

Make any CLI into a single tool MCP server.

Bright Studio Apt – No Walls, No Rules – $0/mo OBO.

Wired and wild. No questions. rm -rf compatible. Cash only. Basement-ish. Just enough, nothing more.

Text 404 to /dev/null for more details!

What's Included?

studio-mcp is the simplest possible stdio Model Context Protocol server.

Everything after the studio-mcp command will be turned into an MCP tool that runs just that command when called by Cursor, Claude, etc.

studio-mcp uses a very simple Mustache-like template syntax in order to tell the LLM how to use your MCP command.

$ npx --silent -y studio-mcp command "{{ required_argument # Description of argument }}" "[optional_args... # any array of arguments]"

studio-mcp turns this into an input schema for the MCP tool so that tool calls know what to send:

{
  "type": "object",
  "properties": {
    "required_argument": { "type": "string", "description": "Description of argument" },
    "optional_args": { "type": "array", "items": { "type": "string" }, "description": "any array of arguments" }
  },
  "required": ["required_argument"]
}

You can run almost any command. Since you're just renting the place, please be a good tenant and don't rm -rf anything.

Move-In

These install instructions are like my lease agreement: full of gotchas. Have your lawyer read it over. (You do have a lawyer right?)

You can install to your system with npm, use npx directly, or install with go install github.com/studio-mcp/studio-mcp@latest

npm install -g studio-mcp

Or download directly from GitHub Releases and add to your PATH yourself.

Unpack (it's an apartment metaphor)

Most MCPs don't run in your shell environment 😭 You'll probably need to add the full path somewhere.

We'll use the MacOS say command as an example command. If you're not on a Mac, use echo (it's worse than useless, but it's easy to understand).

Claude Desktop

Go to the Claude Desktop settings and click Developer > Edit Config. It should open your Claude Desktop MCP configuration. (e.g. ~/Library/Application Support/Claude/claude_desktop_config.json on Mac):

{
  "mcpServers": {
    "say": {
      "command": "studio-mcp",
      "args": ["--silent", "-y", "studio-mcp", "say", "-v", "siri", "{{speech # A concise message to say outloud}}"]
    },
  }
}

Cursor

Add to your ~/.cursor/mcp.json (in your home or project directory) or go to Tools section of the Cursor UI.

{
  "mcpServers": {
    "say": {
      "command": "npx",
      "args": ["--silent", "-y", "studio-mcp", "say", "-v", "siri", "{{speech # A concise message to say outloud}}"]
    },
  }
}

VSCode

It's a lot of the same here.

{
  "mcp": {
    "servers": {
      "echo": {
        "type": "stdio",
        "command": "npx",

        "args": ["--silent", "-y", "studio-mcp", "echo", "{{text#What do you want to say?}}"]
      }
    }
  }
}

Blueprint Syntax

Studio uses blueprints (templates) to keep your studio tidy.

studio-mcp say -v "{{voice# Choose your Mac say voice}}" "[args...#Any additional args]"

This creates a Studio server with two arguments: voice and args. Everything after the # will be used as the description for the LLM to understand.

Blueprint templates are a modified mustache format with descriptions: {{name # description}} but they also add shell like optional [--flag] booleans, [optional # an optional string] and [args... # array with 0 or more strings] for additional args:

  • {{name}}: Required string argument
  • [name]: Optional string argument
  • [name...]: Optional array argument (spreads as multiple command line args)
  • [--flag]: Optional boolean named flag that prints --flag only when true.
  • {{name...}}: Required array (1 or more arguments required).

Inside a tag, there is a name and description:

  • name: The argument name that will be shown in the MCP tool schema. Only letter numbers and underscores (dashes and underscores are interchangeable, case-insensitive).
  • description: A description of what the argument should contain. Reads everything after the # to the end of the template tag.

What about {{cool_template_feature: string /[A-Z]+/ # Fancy tags}}?

This is a simple studio, not one of those fancy 1 bedroom flats.

Maybe the landlord will get around to it at some point (but your rent will go up).

Utilities Included

To build and test locally:

make
make test
studio-mcp echo "{{text # what you want said to you}}"

Did something break?

The landlord definitely takes care of the place...

  • more than none tests
  • files! lots of 'em!
  • maybe even some test coverage
  • you still need Proof of Renters Insurance

Uncovered portions are tenant's responsibility. (no one appreciates how hard it is for us landlords)

Home Is Where You Make It

This is your studio too. Bugs, bedbugs, features, ideas? Swing by the repo during open-house:

🏠 https://github.com/studio-mcp/studio-mcp

Lease Terms: MIT

Move in under standard terms, no fine print. Full text here: MIT License.