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

@dackerman-stainless/met-museum-demo-mcp

v0.1.0-alpha.2

Published

The official MCP Server for the Met Museum API

Readme

Met Museum TypeScript MCP Server

It is generated with Stainless.

Installation

Via Claude Desktop

See the user guide for setup.

Once it's set up, find your claude_desktop_config.json file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the following value to your mcpServers section. Make sure to provide any necessary environment variables (like API keys) as well.

{
  "mcpServers": {
    "dackerman_stainless_met_museum_demo_api": {
      "command": "npx",
      "args": ["-y", "@dackerman-stainless/met-museum-demo-mcp"],
      "env": {
        "MET_MUSEUM_DEMO_API_KEY": "My API Key"
      }
    }
  }
}

Filtering tools

You can run the package on the command line to discover and filter the set of tools that are exposed by the MCP Server. This can be helpful for large APIs where including all endpoints at once is too much for your AI's context window.

You can filter by multiple aspects:

  • --tool includes a specific tool by name
  • --resource includes all tools under a specific resource, and can have wildcards, e.g. my.resource*
  • --operation includes just read (get/list) or just write operations

See more information with --help:

$ npx -y @dackerman-stainless/met-museum-demo-mcp --help

All of these command-line options can be repeated, combined together, and have corresponding exclusion versions (e.g. --no-tool).

Use --list to see the list of available tools, or see below.

Available Tools

The following tools are available in this MCP server.

Resource objects:

  • retrieve_objects (read): returns a record for an object, containing all open access data about that object, including its image (if the image is available under Open Access)
  • list_objects (read): returns a listing of all valid Object IDs available to use

Resource departments:

  • list_departments (read): returns a listing of all departments

Resource search:

  • list_search (read): returns a listing of all Object IDs for objects that contain the search query within the object’s data