Esm Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

esm.sh CDN: resolve npm package versions and browse module files. No key required.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant resolve npm package versions and browse module files on the esm.sh CDN, with no API key required.

What you can do
Resolve npm package versions through the esm.sh CDN, so the assistant can look up which versions of a package are available and pick one to reference. Browse the module files that esm.sh serves for a package, letting the assistant inspect what a CDN build exposes. The manifest lists no individual tools, so the exact operations are not documented beyond these two capabilities.
When to use it
Useful when you are working with esm.sh URLs or browser-side ES module imports and want the assistant to check available package versions or inspect the files a CDN build serves, without leaving the conversation.
Requirements
Runs as a local process over stdio, installed from the npm package esm-mcp, so a Node.js runtime and npm are needed. No API key, environment variables or headers are declared. Network access to the esm.sh CDN is implied by its purpose.
Before you install
The server contacts the esm.sh CDN on your behalf, so package names you look up are sent to that third party. It is described as read-only lookups of versions and files; no writing, credentials or payments are indicated. The manifest lists no tools, so review what it actually exposes before relying on it.

Installation

In SourceWeft

  1. Open Esm Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.