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

md-skills-mcp

v1.0.5

Published

Skills MCP Server from your files.

Downloads

10

Readme

Markdown Skills MCP Server

Put your tool files in a folder (subfolders allowed) and expose them as MCP tools.

  • Markdown: Each .tool.md file becomes a tool whose instructions are templated with {{placeholders}}.
  • PowerShell: Each .tool.ps1 file has commented frontmatter metadata plus a script body.
  • TypeScript: Each .tool.ts file exports a description, parameters, and runTool function.

All files must contain .tool. in the end of their filename before the extension, otherwise they are ignored.

Using the MCP server

Example .vscode/mcp.json entries you can use to launch the server from an MCP-capable client.

Add MCP server

{
  "servers": {
    "mdSkills": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "md-skills-mcp",
        "--folder",
        ".github/my-tools" // <-- your tools folder here, not necessary in ".github" folder
      ]
    }
  },
  "inputs": []
}

Notes:

The server only reads the folder at startup (no hot-reload). Invalid or malformed Markdown tools are skipped with a console warning.

Supported tools

Tools can be defined via Markdown, TypeScript, or PowerShell files.

Markdown format

  • Filename: [A-Za-z0-9_]+.tool.md (others and hidden files are ignored).
  • Body: instruction template. Use {{param_name}} placeholders (names must be [A-Za-z0-9_]+). Optional params missing at call time render as empty strings.
---
description: "Greets a user"
name: "Name to greet"
---
Hello, {{name}}

PowerShell format

  • Filename: [A-Za-z0-9_]+.tool.ps1.
  • pwsh must be available on the PATH; scripts run with -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass.
# ---
# description: "Greets a user"
# name: Name to greet
# ---
param(
  [string]$name,
)

"Hello, $name"

TypeScript format

  • Filename: [A-Za-z0-9_]+.tool.ts (others and hidden files are ignored).
  • Exports from example below are required.
  • Dependencies: TypeScript tools can import any packages installed alongside the tool file. The server transpiles .ts files at load time; no prebuild required.
export const description = "Greets a user";

export const parameters = {
  name: "Name to greet",
};

export async function runTool(props: Record<string, unknown>): Promise<unknown> {
  const name = String(props.name || 'stranger');
  return `Hello, ${name}`;
}