mcpize 1.0.25 → 1.0.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +24 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -57,6 +57,30 @@ Browser login opens mcpize.com, you sign in with Google/GitHub/email, and the CL
57
57
  | `mcpize secrets delete <name>` | Delete a secret (alias: `rm`) |
58
58
  | `mcpize doctor` | Run pre-deploy diagnostics |
59
59
  | `mcpize whoami` | Show current authenticated user |
60
+ | `mcpize dev` | Run local dev server with hot reload |
61
+
62
+ ## Local Development
63
+
64
+ Run your MCP server locally with hot reload:
65
+
66
+ ```bash
67
+ # Start local dev server
68
+ mcpize dev
69
+
70
+ # With custom entry point
71
+ mcpize dev src/server.ts
72
+
73
+ # Expose via public tunnel (for testing with Claude/clients)
74
+ mcpize dev --tunnel
75
+
76
+ # Open MCPize Playground for interactive testing
77
+ mcpize dev --playground
78
+
79
+ # Choose tunnel provider (localtunnel, ngrok, cloudflared)
80
+ mcpize dev --tunnel --provider ngrok
81
+ ```
82
+
83
+ The `--playground` flag automatically creates a tunnel and opens the [MCPize Playground](https://mcpize.com/playground) where you can test your server's tools interactively.
60
84
 
61
85
  ## Templates
62
86
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mcpize",
3
- "version": "1.0.25",
3
+ "version": "1.0.26",
4
4
  "description": "Deploy and monetize MCP servers in the cloud",
5
5
  "type": "module",
6
6
  "bin": {