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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@first-to-fly/mcp-setup

v2.0.2

Published

A script to automate MCP server setup

Vulnerabilities

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

Links

Maintainers

setkyarsetkyar

Keywords

Readme

MCP Setup

A streamlined CLI tool to automate the setup of MCP (Multi-Component Platform) servers, including browser tools, extensions, and dependencies.

Overview

@first-to-fly/mcp-setup simplifies the process of setting up an MCP development environment by automating the installation and configuration of required components. It handles repository management, dependency installation, browser setup, and configuration file generation.

Features

  • ✅ Dependency installation and build process automation
  • ✅ Playwright Chromium browser installation
  • ✅ Configuration file generation
  • ✅ Cross-platform support (Windows, macOS, Linux)
  • ✅ Intelligent error handling and recovery

Installation & Usage

You can run this tool directly using npx without installing it locally:

npx @first-to-fly/mcp-setup

Or if you prefer to install it globally:

npm install -g @first-to-fly/mcp-setup
mcp-setup

Prerequisites

The following tools need to be installed on your system:

  • Node.js & npm
  • Git
  • Python
  • uv (Python environment manager)
  • Bun

The script will check for these dependencies and provide installation guidance if any are missing.

What It Does

When you run this tool, it performs the following actions:

  1. Prerequisites Check - Verifies all required tools are installed
  2. Directory Setup - Creates necessary directories
  3. Dependency Installation - Installs and builds all required dependencies
  4. Browser Setup - Installs Playwright Chromium
  5. Configuration - Generates the .roo/mcp.json configuration file

After setup is complete, the tool provides instructions for running the Browser Tools Server and installing the Chrome extension.

Requirements

  • API Key: You'll need a Google Gemini API key, which you can obtain from Google AI Studio

Troubleshooting

Browser Installation

If the Chromium browser path cannot be automatically detected, you may need to manually update the path in the generated .roo/mcp.json file.

SSH Keys

For private repositories, ensure your SSH keys are properly set up for GitHub access. The tool uses SSH URLs for repository access.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch: git checkout -b feature/amazing-feature
  3. Commit your changes: git commit -m 'Add some amazing feature'
  4. Push to the branch: git push origin feature/amazing-feature
  5. Open a Pull Request