Cdnjs Mcp

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

Search JavaScript libraries on cdnjs. No key required.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant search JavaScript libraries hosted on cdnjs, with no API key required.

What you can do
  • Search JavaScript libraries on cdnjs and return matching results to the assistant.
  • No tool list is published, so capabilities beyond library search are not documented.
When to use it
Useful when you want an assistant to look up JavaScript libraries and their availability on cdnjs while working on front-end code or picking a dependency.
Requirements
Runs as a local process on the user's machine, installed from the npm package cdnjs-mcp over stdio. Desktop only; no web executable. No authentication, environment variables or headers are declared.
Before you install
No credentials are requested. Search queries are sent to cdnjs, so lookups leave the local machine. The tool set is not documented, so review what it exposes before relying on it.

Installation

In SourceWeft

  1. Open Cdnjs 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.