tappy-mcp 0.1.1

MCP management + inspector + monitoring CLI: discover, configure, run, inspect and monitor MCP servers across AI clients.

Tappy

One CLI to manage, inspect and monitor every MCP server you run.

Works across Claude Desktop, Claude Code, Cursor — and any client with an mcpServers config.

Installation

Requires Python 3.11+. The package is tappy-mcp; it installs the tappy command.

pip install tappy-mcp

Or, isolated in its own environment (recommended for CLI tools):

pipx install tappy-mcp
# or
uv tool install tappy-mcp

Or run it instantly without installing (the npx equivalent):

uvx tappy-mcp status

Verify the install:

tappy --version
tappy help          # grouped overview of every command

Quick start

tappy list            # every server across every client
tappy status          # ...with live health, latency and tool counts
tappy inspect <name>  # full report: status + tools + resources + prompts
tappy watch           # live, auto-refreshing health monitor

What it does

MCP servers are the plugins that give AI tools their real-world powers — but each AI client stores them in its own JSON config file, with no way to see whether a server actually works or what it exposes. Tappy reads every client's config into one view and lets you:

• Manage — add / remove / enable / disable servers without hand-editing JSON. Every write is atomic, diff-previewable (--dry-run), backed up first, and reversible with tappy restore.
• Inspect — talk the real MCP protocol: list a server's tools/resources/prompts, call a tool, read a resource, render a prompt — even against a server that isn't installed anywhere yet (--command / --url).
• Monitor — status / watch / probe show live health, handshake latency and tool counts, probed concurrently over the protocol.
• Secure — pin a server's tool definitions, then verify (or just status) flags if they change behind your back — catching post-approval "rug-pulls".
• Standardize — a git-tracked team registry: apply provisions it to everyone, lint gates CI on drift, sync copies servers between clients.

Every data command supports --json and meaningful exit codes, so it drops straight into scripts, dotfiles and CI.

Documentation

• Full README — features, CLI reference, architecture
• User Guide — hands-on manual: every command, workflows, scripting, troubleshooting
• Changelog
• Issues

License

MIT