Frequently Asked Questions

MCPize is a marketplace and managed hosting platform for Model Context Protocol (MCP) servers. Deploy your MCP server with one click and get a production URL like {slug}.mcpize.run. We handle infrastructure, scaling, billing, and OAuth so you can focus on building.

Model Context Protocol is an open standard created by Anthropic that enables AI applications to securely connect with external data sources and tools. It provides a standardized way for AI systems to access databases, APIs, file systems, and other services through a unified protocol.

MCPize offers 6 hosting tiers: Free ($0, 250K requests/mo, 0.5 vCPU, 512MB), Starter ($9, 1M requests, 1GB), Pro ($29, 5M requests, 1 vCPU), Team ($79, 10M requests, 1.5 vCPU, 2GB), Scale ($179, 15M requests, 2 vCPU, 4GB), and Enterprise (custom, 4-8 vCPU). All plans include GitHub deploy and automatic scaling.

Yes! The Free plan includes 250K requests/month, 0.5 vCPU, 512MB memory, 1 repository, GitHub push deploy, 1 secret, and 7-day log retention. Perfect for hobby projects and testing. Scale to zero when idle to minimize costs.

Each plan has limits on: requests/month (250K to 15M+), CPU (0.5-2+ vCPU), memory (512MB-4GB+), concurrent instances (1-10+), repositories (1-20+), environments (1-5+), secrets (1-100+), and log retention (7-90+ days). See our pricing page for full details.

Yes! Any developer can deploy MCP servers on MCPize. Connect your GitHub repo, push code, and get a production URL instantly. You keep 85% of subscription revenue if you monetize your server.

TypeScript is fully supported with automatic builds. Python SDK and templates are in active development (Phase 3). PHP support is planned (Phase 4). STDIO-based servers are automatically bridged to HTTP transport.

Two ways: (1) Connect GitHub and deploy on push automatically, or (2) Use CLI with `mcpize deploy`. Add a mcpize.yaml manifest to configure runtime, secrets, and settings. We auto-detect TypeScript projects without config.

MCPize automatically bridges STDIO servers to HTTP. Our runtime detects if your server uses STDIO transport and wraps it with an HTTP adapter. No code changes needed for most cases.

Yes! MCPize CLI supports OpenAPI to MCP conversion in under 5 minutes. Run `mcpize init my-api --template typescript/openapi --from-url https://api.example.com/openapi.yaml` then `mcpize deploy`. Each OpenAPI endpoint becomes an MCP tool automatically. Works with any OpenAPI 3.x spec (URL or local file).

The CLI (`npm install -g @mcpize/cli`) provides full control: `mcpize login` for auth, `mcpize init` to scaffold projects (TypeScript, OpenAPI templates), `mcpize deploy` for deployments, `mcpize logs` for streaming logs, `mcpize secrets` for secret management, and `mcpize status` to check server health. Works great for CI/CD automation.

Developers keep 85% of all subscription revenue. MCPize takes 15% to cover infrastructure (GCP Cloud Run, storage, bandwidth), billing processing, support, and platform maintenance.

Payouts are processed monthly via Stripe Connect. You set your own pricing for subscribers. Revenue is calculated after Stripe processing fees, then split 85/15.

Hosting plans are billed monthly through Stripe. Usage beyond plan limits triggers overage charges ($0.02 per 1K requests). Dashboard shows real-time usage so you can monitor consumption.

Yes, downgrade or cancel your hosting plan anytime from the dashboard. Changes take effect at the next billing cycle. No long-term commitments required.

MCPize supports API key authentication and OAuth 2.1 with PKCE. Our gateway validates tokens before routing traffic to your server. OAuth flows use Supabase Auth with support for email, magic links, and social providers.

Each server runs in an isolated Google Cloud Run environment with its own service account. Secrets are encrypted at rest using pgcrypto. We implement rate limiting per billing tier, OAuth token scoping, and per-service network isolation. SOC 2 certification is on our roadmap.

All plans include Cloud Logging access. Retention varies by tier: Free/Starter get 7 days, Pro gets 30 days + 90-day BigQuery export, Team gets 60 days, Scale gets 90 days + 180-day BigQuery. Logs are accessible via dashboard and CLI.

Yes! Enterprise plans ($500+/mo) include: custom resources (4-8 vCPU, 4-8GB RAM), unlimited repos and environments, BYO GCP project option, private VPC peering, audit logs, custom log retention (up to 365 days), SSO, and dedicated support with custom SLAs.

Absolutely. MCPize runs on Google Cloud Run with automatic scaling, health checks, and production-grade infrastructure. Enterprise customers can configure VPC egress controls, IP allowlists, and get custom SLA guarantees.