feat: next.js support

.gitignore

@@ -71,4 +71,7 @@ vite.config.ts.timestamp-*
 # Coding agents
 CLAUDE.md
 .claude/
-.mcp.json
+.mcp.json
+
+/.yalc/
+yalc.lock

README.md

@@ -56,6 +56,33 @@ tidewave({
 });
 ```
 
+### HTTP MCP via Next.js Integration
+
+Tidewave provides seamless integration with Next.js through a simple handler
+function. Add the handler to your API routes:
+
+**Pages Router** - Create `pages/api/tidewave/[...all].ts`:
+
+```typescript
+import { toNodeHandler } from 'tidewave/next-js';
+
+// Optional tidewave internal config
+export default toNodeHandler({
+  allowRemoteAccess: false,
+  allowedOrigins: [],
+});
+
+// Next.js specific config
+export const config = {
+  runtime: 'nodejs',
+  api: {
+    bodyParser: false,
+  },
+};
+```
+
+This exposes MCP endpoints at `/api/tidewave/mcp` and `/api/tidewave/shell`.
+
 ### CLI Usage
 
 Tidewave also provides the MCP features over a CLI tool. Use it directly via

eslint.config.js

@@ -23,8 +23,17 @@ export default [
       '@typescript-eslint': tseslint,
     },
     rules: {
+      'no-unused-vars': 'off',
       // TypeScript rules
-      '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
+      '@typescript-eslint/no-unused-vars': [
+        'error',
+        {
+          args: 'after-used',
+          argsIgnorePattern: '^_',
+          varsIgnorePattern: '^_',
+          caughtErrorsIgnorePattern: '^_',
+        },
+      ],
       '@typescript-eslint/explicit-function-return-type': 'warn',
       '@typescript-eslint/no-explicit-any': 'warn',
       '@typescript-eslint/no-var-requires': 'error',