Twelve direct answers about MCPizy — what it is, how it works with Claude / Cursor / Windsurf, pricing, privacy, and the optimization layer. Looking for something else? Email [email protected].
MCPizy is the runtime and optimization layer for Model Context Protocol (MCP) servers. It lets developers discover MCP servers in a curated marketplace, install them in one command, monitor usage, and cut Claude API costs by 30-60% with a local proxy that caches idempotent tool calls.
An MCP server is a small process that exposes tools, resources, or prompts to an AI agent through the Model Context Protocol. Examples include a Postgres MCP server (lets Claude query your database), a Browser MCP server (lets Claude open URLs), or a Stripe MCP server (lets Claude read your account). MCPizy maintains a catalog of 300+ verified MCP servers.
The MCPizy proxy wraps your local MCP servers and caches deterministic tool responses (e.g. "list files in repo", "get user profile"). When Claude calls the same tool with the same arguments inside a session, the proxy returns the cached response instead of re-executing. On chained MCP workflows we typically observe 30-60% cost reduction with no behaviour change.
Starter is free forever (5 MCPs, 1,000 tool calls/month, 7-day history) with no credit card required. Pro is $19/month (unlimited MCPs, 100,000 calls, 90 days history, full analytics). Team is $49/month (everything in Pro + multi-user, SSO, 500,000 calls, 1-year history). Annual billing knocks 20% off — see the pricing page.
Starter calls queue until next month so you never get billed unexpectedly. Pro and Team activate metered overage at a per-call rate — no hard cut-off, no surprise blocks. You can set a hard cap in the billing portal if you want a strict ceiling.
Yes. MCPizy speaks the MCP protocol natively, so any MCP-compatible client works: Claude Code, Claude Desktop, Cursor (.cursor/mcp.json), Windsurf, VS Code with Copilot Chat, Zed, and any custom client built on the MCP SDK. The same install command targets all of them — only the config file path differs.
Yes. The MCPizy proxy wraps any MCP server — public or private. Add a custom server entry to ~/.claude.json (or .cursor/mcp.json) and run `mcpizy proxy install`. Your private servers will appear in your dashboard alongside the marketplace ones, with the same observability and caching benefits.
Only metadata: tool names, timestamps, latency, and payload sizes. We never collect your prompts, tool inputs, tool outputs, file contents, or source code. Authentication uses Clerk (EU region), data is stored in Supabase EU (Frankfurt), and nothing leaves your machine on the proxy hot path. Full detail at /privacy.
Yes. All data is stored in Supabase EU region. Authentication and billing entities (Clerk, Stripe) operate from EU subsidiaries. We sign Data Processing Agreements with paid plans on request. You can export and delete all your data from the account settings at any time.
APC is a technique from NeurIPS 2025 that caches generalized execution plans after the first successful run. When an agent encounters a similar task pattern, it executes the cached plan directly instead of going through free-form ReAct reasoning. MCPizy's implementation reaches ~67% token reduction and ~80% cost reduction on repeated patterns. See /guides for the deep dive.
Yes — MCPizy's hosted execution mode runs whitelisted MCP servers on our infrastructure. Connect your account credentials once (encrypted at rest), then invoke recipes from the dashboard or via the API without any local install. Currently available for select OAuth-friendly servers; see the marketplace badge.
Catalogs index MCPs; MCPizy runs them. We provide the same discovery experience plus a local proxy that observes and optimises tool calls, a recipe engine that combines multiple MCPs into multi-step workflows, and team-level analytics. Pure catalogs stop at the install command — MCPizy starts there.
Try MCPizy free — no credit card. Or browse the marketplace and pricing.