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

figma-mcp-lor

v0.1.4

Published

Scaffold a local Figma MCP server into your project (init command).

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

dray.devdray.dev

Keywords

Readme

figma-mcp-lor

A small CLI to scaffold a local figma-mcp-server folder into any project (so the whole team can share the same MCP tools setup).

Quickstart (recommended)

From your project root:

npx -y figma-mcp-lor@latest init
export FIGMA_TOKEN=...
npx -y figma-mcp-lor@latest setup

What you get:

  • .figma-mcp-server/ (the local MCP server)
  • .vscode/mcp.json (VS Code workspace MCP config)

Then restart VS Code so it picks up .vscode/mcp.json.

Commands

init

Creates .figma-mcp-server/ and writes .vscode/mcp.json (unless you disable it).

npx -y figma-mcp-lor@latest init [--dir <projectRoot>] [--server-dir <relPath>] [--vscode-mcp <relPath>] [--force]

setup

Runs a one-command setup to make sure it can work:

  • npm install inside the server folder
  • validates FIGMA_TOKEN by calling https://api.figma.com/v1/me
export FIGMA_TOKEN=...
npx -y figma-mcp-lor@latest setup [--dir <projectRoot>] [--server-dir <relPath>]

Token sharing strategy

  • Each developer keeps their own FIGMA_TOKEN locally (do not commit .env).
  • The shared .vscode/mcp.json references ${env:FIGMA_TOKEN}.

Publish to share

This folder is an npm package. Publish it to npm or your private registry:

cd figma-mcp-lor
npm publish

Or install from git:

npm i -g <git-url>