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

mcp-inspect

v1.0.5

Published

A terminal UI (TUI) inspector for Model Context Protocol (MCP) servers

Readme

mcp-inspect

A terminal UI (TUI) inspector for Model Context Protocol (MCP) servers. Inspect server capabilities, resources, prompts, tools, message history, and MCP server logs, and test MCP tools, all in an interactive terminal interface. Similar to MCP Inspector but works from any terminal session, including inside of sandboxes or containers.

mcp-inspect TUI

🎥 Watch the Demo: Check out the mcp-inspect Introduction and Demo video to see how to inspect MCP servers, test tools, browse resources, and monitor server activity—all from your terminal.

Installation

npm install -g mcp-inspect

Or use via npx:

npx mcp-inspect <config-file.json>

Usage

mcp-inspect <config-file.json>

Where config-file.json is your MCP configuration file (typically mcp.json).

Configuration File Format

The configuration file should follow the MCP configuration format:

{
  "mcpServers": {
    "server-name": {
      "type": "stdio",
      "command": "node",
      "args": ["server.js"]
    },
    "another-server": {
      "type": "sse",
      "url": "http://localhost:6969/sse"
    }
  }
}

Supported transport types:

  • stdio - Standard input/output communication
  • sse - Server-Sent Events
  • streamableHttp - Streamable HTTP

Features

  • Server Management: Connect to multiple MCP servers simultaneously
  • Resource Inspection: Browse and view available resources
  • Prompt Templates: View and inspect prompt templates
  • Tool Testing: Test MCP tools with custom inputs and view results
  • Message History: Track all requests, responses, and notifications
  • Logging: View server stderr output and notifications
  • Interactive UI: Navigate with keyboard shortcuts

Keyboard Shortcuts

Global

  • ESC - Exit application
  • Ctrl+C - Exit application
  • Tab / Shift+Tab - Cycle focus between panes
  • / - Navigate lists and scroll content
  • Enter - Select item / Test tool
  • + - Zoom to full-screen modal view (in details panes)

Tabs

  • Quick switch to tabs:
    • I - Info
    • R - Resources
    • P - Prompts
    • T - Tools
    • M - Messages
    • L - Logging

Server Management

  • C - Connect to selected server (when disconnected or in error state)
  • D - Disconnect from selected server (when connected)

Tool Testing

  • Enter - Test tool (from tool list or details view)

Development

# Install dependencies
npm install

# Build
npm run build

# Run in development mode
npm run dev <config-file.json>

License

MIT

Contributing

Contributions welcome! Please open an issue or submit a pull request.