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

@thoughtindustries/vitally

v0.1.0

Published

MCP server wrapping the Vitally customer success platform API, packaged as a Docker container.

Readme

vitally MCP Server

MCP server wrapping the Vitally customer success platform API, packaged as a Docker container.

Prerequisites

  • VITALLY_API_KEY — API secret token from Vitally Settings > Integrations > REST API
  • VITALLY_BASE_URLhttps://{subdomain}.rest.vitally.io (US) or https://rest.vitally-eu.io (EU)

Curated tools

| Tool | Endpoint | Description | |------|----------|-------------| | list_accounts | GET /resources/accounts | Paginated list of accounts. Supports status filter (active/churned). | | get_account | GET /resources/accounts/{id} | Get account details by Vitally ID or externalId. | | get_account_health_scores | GET /resources/accounts/{id}/healthScores | Get account health score breakdown. | | list_users | GET /resources/users | Paginated list of all users. | | get_user | GET /resources/users/{id} | Get user details by Vitally ID or externalId. | | search_users | GET /resources/users/search | Find users by email, externalId, or email subdomain. | | list_tasks | GET /resources/tasks | Paginated list of tasks with optional archived/source filters. | | create_task | POST /resources/tasks | Create/upsert a task (unique on externalId). | | list_notes | GET /resources/notes | Paginated list of notes with optional archived/source filters. | | create_note | POST /resources/notes | Create a note with HTML body support. | | list_nps_responses | GET /resources/npsResponses | Paginated list of NPS responses. |

All other 43 endpoints (conversations, projects, updates, deletes, per-account/org variants, categories) are accessible via search_actions + execute_action.

Run locally (stdio, for Claude Desktop)

docker build -t vitally-mcp -f servers/vitally/Dockerfile .
docker run -i --rm \
  -e VITALLY_API_KEY=your-api-key \
  -e VITALLY_BASE_URL=https://yoursubdomain.rest.vitally.io \
  vitally-mcp

Claude Desktop config

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "vitally": {
      "command": "docker",
      "args": ["run", "-i", "--rm",
        "-e", "VITALLY_API_KEY",
        "-e", "VITALLY_BASE_URL",
        "vitally-mcp:latest"
      ],
      "env": {
        "VITALLY_API_KEY": "<your secret token>",
        "VITALLY_BASE_URL": "https://yoursubdomain.rest.vitally.io"
      }
    }
  }
}

Run as HTTP server (shared deployment)

docker run -p 3000:3000 \
  -e MCP_TRANSPORT=http \
  -e VITALLY_API_KEY=your-api-key \
  -e VITALLY_BASE_URL=https://yoursubdomain.rest.vitally.io \
  vitally-mcp

Then connect via Streamable HTTP at http://your-host:3000/mcp.