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

levisnkyyyy-s3

v0.1.4

Published

MCP server for deploying websites to S3 with simple API integration

Readme

levisnkyyyy-s3

An MCP (Model Context Protocol) server that provides tools for deploying websites directly to AWS S3.

Installation

npm install -g levisnkyyyy-s3

Or install locally in your project:

npm install levisnkyyyy-s3

Configuration

Set the required environment variables:

export AWS_ACCESS_KEY=your-access-key
export AWS_ACCESS_SECRET=your-secret-key
export S3_BUCKET_NAME=your-bucket-name
export AWS_REGION=us-east-1  # Optional, defaults to us-east-1

Usage

Running the MCP Server

If installed globally:

levisnkyyyy-s3

Or run directly with npx:

npx levisnkyyyy-s3

With environment variables:

AWS_ACCESS_KEY=your-key AWS_ACCESS_SECRET=your-secret S3_BUCKET_NAME=your-bucket npx levisnkyyyy-s3

Claude Desktop Configuration

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "levisnkyyyy-s3": {
      "command": "npx",
      "args": ["levisnkyyyy-s3"],
      "env": {
        "AWS_ACCESS_KEY": "your-access-key",
        "AWS_ACCESS_SECRET": "your-secret-key",
        "S3_BUCKET_NAME": "your-bucket-name",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Available Tools

deploy_website

Deploys a website to S3 by uploading the contents of the dist folder.

Parameters:

  • website_path (string, required): Absolute path to the website project directory

Example:

Deploy the website from /home/user/my-react-app

The tool will:

  1. Automatically append /dist to your website path
  2. Validate the dist directory exists
  3. Upload all files from the dist folder recursively to S3
  4. Preserve the directory structure
  5. Use the original project directory name as the S3 prefix

Features

  • Deploys websites by automatically uploading the dist folder
  • Uploads entire directories with subdirectories
  • Preserves directory structure in S3
  • Excludes hidden files and folders (starting with '.')
  • Provides detailed upload progress and results
  • Shows which files succeeded or failed
  • Handles large directories with timeout protection
  • Clear error messages for troubleshooting

Error Handling

The server handles various error scenarios:

  • Directory not found
  • Path is not a directory
  • AWS authentication errors
  • S3 upload failures for individual files
  • Missing environment variables

Requirements

  • Node.js 16 or higher
  • Valid AWS credentials with S3 write permissions
  • An S3 bucket configured for your deployments