Deploy and monetize MCP servers in the cloud
npm install mcpizeDeploy and monetize MCP servers in the cloud.
``bash`
npm install -g mcpize
`bashLogin to MCPize
mcpize login
Authentication
`bash
Browser login (recommended) - opens mcpize.com
mcpize loginEmail/password login
mcpize login --email
`Browser login opens mcpize.com, you sign in with Google/GitHub/email, and the CLI receives your session automatically.
Commands
| Command | Description |
|---------|-------------|
|
mcpize login | Authenticate via browser (recommended) |
| mcpize login --email | Authenticate with email/password |
| mcpize logout | Log out from MCPize |
| mcpize init [name] | Create a new MCP server project |
| mcpize analyze | Generate mcpize.yaml from existing project |
| mcpize link | Link current directory to an existing server |
| mcpize deploy | Deploy to MCPize Cloud |
| mcpize status | Show server status and deployments |
| mcpize logs | View runtime and build logs |
| mcpize secrets list | List environment secrets |
| mcpize secrets set | Set a secret |
| mcpize secrets delete | Delete a secret (alias: rm) |
| mcpize doctor | Run pre-deploy diagnostics |
| mcpize whoami | Show current authenticated user |
| mcpize dev | Run local dev server with hot reload |Local Development
Run your MCP server locally with hot reload:
`bash
Start local dev server
mcpize devWith custom entry point
mcpize dev src/server.tsExpose via public tunnel (for testing with Claude/clients)
mcpize dev --tunnelOpen MCPize Playground for interactive testing
mcpize dev --playgroundChoose tunnel provider (localtunnel, ngrok, cloudflared)
mcpize dev --tunnel --provider ngrok
`The
--playground flag automatically creates a tunnel and opens the MCPize Playground where you can test your server's tools interactively.Templates
Create a new project from a template:
`bash
TypeScript (default)
mcpize init my-serverGenerate from OpenAPI spec
mcpize init my-api --template openapi --from-url https://api.example.com/openapi.jsonPython
mcpize init my-server --template python
`Analyze
Generate
mcpize.yaml from an existing MCP server project:`bash
Analyze current directory
mcpize analyzePreview without saving
mcpize analyze --dry-runOverwrite existing mcpize.yaml
mcpize analyze --forceSkip confirmation prompt
mcpize analyze --yes
`The analyze command:
- Detects runtime (TypeScript, Python, Container)
- Extracts start command from package.json/Dockerfile
- Identifies required credentials from code
- Generates a ready-to-deploy manifest
Secrets Management
`bash
Set a secret
mcpize secrets set API_KEY sk-xxxSet from file
mcpize secrets set CREDENTIALS --from-file ./credentials.jsonList secrets (names only)
mcpize secrets listExport secrets
mcpize secrets export --format env
`Logs
`bash
View runtime logs
mcpize logsView build logs
mcpize logs --type buildFollow logs in real-time
mcpize logs --followFilter by severity
mcpize logs --severity ERROR
`Linking
`bash
Link current directory to an existing server
mcpize linkLink to a specific server
mcpize link --server Force re-link
mcpize link --force
`Options
`bash
Use specific server
mcpize status --server Output as JSON
mcpize status --jsonDeploy without waiting
mcpize deploy --no-waitAuto-create server if not linked
mcpize deploy --yesForce refresh (ignore cache)
mcpize status --refresh
`Global Options
| Option | Description |
|--------|-------------|
|
--token | API token (overrides MCPIZE_TOKEN env and saved session) |Environment Variables
| Variable | Description |
|----------|-------------|
|
MCPIZE_TOKEN | API token (alternative to mcpize login`) |MIT