tidewave 0.1.0 → 0.2.4

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.
package/README.md CHANGED
@@ -20,7 +20,7 @@ Simply configure your editor to run `tidewave` in the same directory as your
20
20
 
21
21
  ```bash
22
22
  npx tidewave mcp
23
- # or
23
+ # or with Bun
24
24
  bunx tidewave mcp
25
25
  # or with Deno
26
26
  deno run npm:tidewave mcp
@@ -30,6 +30,32 @@ Available MCP options:
30
30
 
31
31
  - `--prefix path` - Specify the directory to find the `package.json` file
32
32
 
33
+ ### HTTP MCP via Vite Plugin
34
+
35
+ Tidewave also provides HTTP-based MCP access through a Vite plugin for
36
+ development environments. Add the plugin to your `vite.config.js`:
37
+
38
+ ```javascript
39
+ import { defineConfig } from 'vite';
40
+ import tidewave from 'tidewave/vite-plugin';
41
+
42
+ export default defineConfig({
43
+ plugins: [tidewave()],
44
+ });
45
+ ```
46
+
47
+ This exposes MCP endpoints at `/tidewave/mcp` and `/tidewave/shell` during
48
+ development.
49
+
50
+ Configuration options:
51
+
52
+ ```javascript
53
+ tidewave({
54
+ allowRemoteAccess: false, // Allow access from remote IPs
55
+ allowedOrigins: ['localhost'], // Allowed origins: defaults to the Vite's host+port
56
+ });
57
+ ```
58
+
33
59
  ### CLI Usage
34
60
 
35
61
  Tidewave also provides the MCP features over a CLI tool. Use it directly via
@@ -0,0 +1,2 @@
1
+ #!/usr/bin/env node
2
+ export {};