Documentation
Everything you need to get started with MCPizy.
Proxy Quickstart
The MCPizy proxy wraps your MCP servers on your own machine: it caches idempotent tool responses, streams telemetry to your dashboard, and typically cuts your Claude API bill by 30–60% on chained workflows. Setup takes about 2 minutes.
1. Install once
npm install -g mcpizyOr prefix every command with npx.
3. Wrap your MCPs
mcpizy proxy installWe back up your ~/.claude.json first. Revert anytime with mcpizy proxy uninstall.
Privacy: Only metadata (tool name, latency, payload size) is streamed to mcpizy.com. Your code, prompts, and response bodies never leave your machine.
Getting Started
1. Create an account
Sign up at mcpizy.com/sign-up with Google or email.
2. Install the observer
Run this in your terminal:
npx mcpizy initThis adds a hook to your Claude Code that sends tool call metadata (tool name, timestamp, project) to your MCPizy dashboard. No code or file contents are ever sent.
3. Browse & install MCPs
Find MCPs in the marketplace or install via CLI:
mcpizy search databasemcpizy install postgres4. Monitor your MCPs
Your dashboard auto-populates as you use Claude. See which MCPs are active, view analytics, and track usage over time.
CLI Reference
| Command | Description |
|---|---|
| npx mcpizy init | Install observer hook + configure API key |
| npx mcpizy install <name> | Install an MCP from the marketplace into .claude.json |
| npx mcpizy search <query> | Search the marketplace from your terminal |
| npx mcpizy status | Check hook installation and API key status |
API Reference
/api/healthService health check (public)
/api/marketplaceBrowse MCP catalog (public). Params: q, category, limit
/api/ingestSend tool call observations. Auth: Bearer API key
/api/statusMCP status + pulse (auth required)
/api/activityActivity log. Params: mcp, category, project, limit
/api/analyticsUsage analytics aggregation
/api/machines/[id]Per-MCP detail with tool breakdown