home / mcp / jsr mcp server

JSR MCP Server

Provides semantic search, package details, downloads, and docs access for JSR via MCP.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "orgsofthq-jsr": {
      "command": "path/to/your/deno",
      "args": [
        "run",
        "--allow-net=jsr.io,api.jsr.io,cloud.orama.run",
        "--allow-run",
        "jsr:@orgsoft/jsr@^1",
        "mcp"
      ]
    }
  }
}

You run an MCP server for the @orgsoft/jsr package explorer to expose JSR data to AI assistants and other clients. This MCP server lets you interact with JSR’s search, package details, downloads, and docs through a standardized protocol, enabling practical AI-assisted workflows and automation.

How to use

Use the MCP server by connecting your MCP client to the stdio-based server entry exposed by Deno. This setup lets you perform semantic searches, discover related packages, fetch package details and download statistics, and retrieve files or docs for any JSR package.

How to install

Prerequisites you need before starting are the latest version of Deno and a compatible MCP client.

# Install Deno if you don’t have it already
# Follow your platform’s install instructions for Deno
```

Next, configure the MCP server entry in your client configuration. You will run Deno with the MCP command for @orgsoft/jsr as shown below.

MCP server configuration (stdio)

{
  "mcpServers": {
    "jsr": {
      "command": "path/to/your/deno",
      "args": [
        "run",
        "--allow-net=jsr.io,api.jsr.io,cloud.orama.run",
        "--allow-run",
        "jsr:@orgsoft/jsr@^1",
        "mcp"
      ]
    }
  }
}

Security notice

Use the minimal permissions necessary and pin package versions where possible. The setup uses a read-only doc command via a safe permission model, but you should review all code you execute in your environment.

Usage examples you can run with your MCP client

Once the MCP server is running, you can issue commands through your MCP client to explore JSR data. Typical actions include searching for web frameworks, discovering related packages, or inspecting package details and download metrics.

Available tools

search

Semantically search JSR packages with optional limits to control result count.

find_similar

Find packages similar to a given package name, returning relevance scores.

discover

Discover packages by category or use case with optional result limiting.

compare

Compare multiple packages side-by-side to evaluate features and stats.

scope_packages

List all packages within a specified JSR scope.

package_details

Get detailed information for a specific package within a scope.

package_downloads

View download statistics for a package with rolling window summaries.

package_file

Retrieve a file from a specific package version.

docs

Fetch documentation for a module within a package.

search_status

Check the health and status of the search capabilities.