feat: get_logs tool (#34)

Author: zoey

.github/workflows/ci.yml

@@ -12,31 +12,24 @@ jobs:
   lint:
     runs-on: ubuntu-latest
 
-    strategy:
-      matrix:
-        node-version: [18, 20, 22]
-
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
 
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node-version }}
-          cache: 'npm'
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
 
       - name: Install dependencies
-        run: npm ci
+        run: bun install
 
       - name: Check code formatting
-        run: npm run format:check
+        run: bun format:check
 
       - name: Run ESLint
-        run: npm run lint
+        run: bun lint
 
       - name: Type check
-        run: npm run type:check
+        run: bun type:check
 
   test:
     runs-on: ubuntu-latest

.github/workflows/publish.yml

@@ -143,6 +143,80 @@ export const config = {
 
 This exposes the MCP endpoint at `/tidewave/mcp`.
 
+**Logging** (optional): To capture application logs for debugging via the
+`get_logs` MCP tool, add OpenTelemetry instrumentation.
+
+Create an `instrumentation.ts` file in your project root:
+
+```typescript
+// instrumentation.ts
+import { NodeSDK } from '@opentelemetry/sdk-node';
+
+export async function register() {
+  const runtime = process.env.NEXT_RUNTIME;
+  const env = process.env.NODE_ENV;
+
+  if (runtime === 'nodejs' && env === 'development') {
+    const { TidewaveSpanProcessor, TidewaveLogRecordProcessor } = await import(
+      'tidewave/next-js/instrumentation'
+    );
+
+    const sdk = new NodeSDK({
+      spanProcessors: [new TidewaveSpanProcessor()],
+      logRecordProcessors: [new TidewaveLogRecordProcessor()], // Optional
+    });
+
+    sdk.start();
+  }
+}
+```
+
+This captures:
+
+- Console logs (`console.log`, `console.error`, etc.) - automatic when you
+  import the module
+- Next.js HTTP request/response spans (`GET /api/users 200 45ms`) - via
+  `TidewaveSpanProcessor`
+- OpenTelemetry logger logs - via `TidewaveLogRecordProcessor` (optional)
+
+#### With Existing OpenTelemetry Setup
+
+If you already have custom OpenTelemetry instrumentation, simply add the
+Tidewave processors to your existing setup:
+
+```typescript
+// instrumentation.ts
+import { NodeSDK } from '@opentelemetry/sdk-node';
+import { BatchSpanProcessor } from '@opentelemetry/sdk-trace-node';
+
+export async function register() {
+  const runtime = process.env.NEXT_RUNTIME;
+  const env = process.env.NODE_ENV;
+
+  // Your existing configuration
+  const sdkConfig = {
+    spanProcessors: [new BatchSpanProcessor(yourExporter)],
+    logRecordProcessors: [],
+  };
+
+  // Conditionally add Tidewave processors in development
+  if (runtime === 'nodejs' && env === 'development') {
+    const { TidewaveSpanProcessor, TidewaveLogRecordProcessor } = await import(
+      'tidewave/next-js/instrumentation'
+    );
+
+    sdkConfig.spanProcessors.push(new TidewaveSpanProcessor());
+    sdkConfig.logRecordProcessors.push(new TidewaveLogRecordProcessor());
+  }
+
+  const sdk = new NodeSDK(sdkConfig);
+  sdk.start();
+}
+```
+
+This allows Tidewave to capture logs alongside your existing OpenTelemetry setup
+without conflicts.
+
 ### CLI Usage
 
 Tidewave also provides the MCP features over a CLI tool. Use it directly via