Registry / web-framework / tidewave

tidewave

JSON →
library0.2.1jsnpmunverified

Tidewave is an MCP (Model Context Protocol) server and library for JavaScript/TypeScript frameworks (Next.js, TanStack, Vite). It provides CLI and programmatic interfaces to expose project context to AI agents. Current stable version 0.6.0, released weekly, requires Node >=18 or Bun >=1.0. Ships TypeScript types. Differentiators: deep integration with modern JS frameworks, lightweight, and supports both stdio and HTTP transport.

npm install tidewave
INSTALL
IMPORT
SIG · TIDEWAVE
T
tidewave
web-frameworkjavascriptv0.2.1
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18223 runs
build_error
glibc
node 18223 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

Tidewave
import { Tidewave } from 'tidewave'
import Tidewave from 'tidewave'
Tidewave is a named export, not default. Use named import.
startMcpServer
import { startMcpServer } from 'tidewave/mcp'
import { startMcpServer } from 'tidewave'
The MCP server functions are in a subpath export. Import from 'tidewave/mcp'.
cli
import { cli } from 'tidewave/cli'
The CLI entry point is exported from 'tidewave/cli'. Not available in the main package.

Initialize Tidewave with project path and optional prefix, then retrieve project context for AI agents.

import { Tidewave } from 'tidewave'; const tw = new Tidewave({ projectPath: process.cwd(), prefix: process.env.TIDEWAVE_PREFIX ?? '' }); async function main() { const context = await tw.getProjectContext(); console.log('Project context:', context); } main();
tidewave --version
Debug
Known issues
breakingIn v0.2.0, project evaluation scoped tool introduced, changing the tool schema. Older tools may not be compatible.
fix
Update to v0.2.3 or later.
affects: >=0.2.0 <0.2.3
deprecatedThe `config` flag was renamed to `projectPath` in v0.1.0. Old flag no longer works.
fix
Use `projectPath` instead of `config`.
affects: <0.1.0
gotchaThe `prefix` option is only applied at the CLI layer. If using programmatic API, you must handle prefixes manually.
fix
Check the CLI documentation for prefix usage; programmatic users ignore prefix.
affects: >=0.1.0
breakingIn v0.2.0, HTTP paths were changed to `/tidewave` prefix. Custom paths may break.
fix
Update any custom HTTP handlers to use the `/tidewave` prefix.
affects: >=0.2.0
gotchaStdio MCP server (v0.1.0) is experimental and may have issues with large project contexts.
fix
Upgrade to v0.2.0+ or use HTTP transport.
affects: >=0.1.0 <0.2.0
Errors
Common errors & fixes
Cannot find module 'tidewave' or its corresponding type declarations.
Missing import or no TypeScript types installed.
fix
Install package: `npm install tidewave` and ensure TypeScript is present (`npm install --save-dev typescript`).
The requested module 'tidewave' does not provide an export named 'startMcpServer'
Importing from wrong subpath.
fix
Change import to: `import { startMcpServer } from 'tidewave/mcp'`
Error: config is not a valid option. Did you mean projectPath?
Using deprecated `config` option.
fix
Use `projectPath` instead.
Upgrade
Version history
0.2.1latest on npm
Audit
Dependencies
typescriptoptionalPeer dependency required for type definitions and compilation of configuration files.
Agent activity
29 hits · last 30 days
node
26
OpenAI (training)
1
Resources
tidewave — npm install tidewave · libregistry