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

mocktail-mcp

v3.1.8

Published

MCP server for managing Mocktail mock API endpoints

Readme

Mocktail MCP Server

An MCP (Model Context Protocol) server that lets AI assistants manage Mocktail mock API endpoints through natural language.

Tools

| Tool | Description | |------|-------------| | list_mocks | List all configured mock endpoints | | create_mock | Create a single mock endpoint | | update_mock | Update an existing mock by ID | | delete_mock | Delete a mock by ID | | import_mocks | Bulk import multiple mock endpoints (skips duplicates) |

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | MOCKTAIL_URL | Yes | Base URL of your Mocktail instance (e.g. http://localhost:4000) | | MOCKTAIL_API_KEY | No | API key, sent as X-API-Key header |

Note: If you're running Mocktail behind a reverse proxy or custom domain (via MOCKTAIL_BASE_URL), use that host as MOCKTAIL_URL (e.g. MOCKTAIL_URL=https://api.mycompany.com).

Setup

npx (Recommended)

Claude Code:

claude mcp add mocktail \
  -e MOCKTAIL_URL=http://localhost:4000 \
  -e MOCKTAIL_API_KEY=your-api-key \
  -- npx mocktail-mcp

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "mocktail": {
      "command": "npx",
      "args": ["mocktail-mcp"],
      "env": {
        "MOCKTAIL_URL": "http://localhost:4000",
        "MOCKTAIL_API_KEY": "your-api-key"
      }
    }
  }
}

From Source (Development)

If you cloned the repo and want to run the MCP server locally:

cd mcp-server && npm install

Claude Code:

claude mcp add mocktail \
  -e MOCKTAIL_URL=http://localhost:4000 \
  -e MOCKTAIL_API_KEY=your-api-key \
  -- node /absolute/path/to/mcp-server/index.js

Claude Desktop:

{
  "mcpServers": {
    "mocktail": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/index.js"],
      "env": {
        "MOCKTAIL_URL": "http://localhost:4000",
        "MOCKTAIL_API_KEY": "your-api-key"
      }
    }
  }
}

Usage Examples

Once connected, you can use natural language:

  • "List all my mock endpoints"
  • "Create a GET /api/users mock that returns a list of 3 users"
  • "Delete mock endpoint #5"
  • "Import mock endpoints for a blog API with posts, comments, and authors"