baichuan-mcp-servers: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build Commands

pnpm install              # Install dependencies
pnpm build                # Build all packages (UI bundle + TypeScript)
pnpm dev                  # Watch mode for all packages
pnpm lint                 # Type check all packages (tsc --noEmit)
pnpm test                 # Run tests
pnpm clean                # Clean all build outputs
pnpm inspector            # Launch MCP Inspector for interactive debugging

Single Package Commands

pnpm --filter @baichuan-ai/<package-name> build   # Build specific package
pnpm --filter @baichuan-ai/<package-name> dev     # Watch mode for specific package
pnpm --filter @baichuan-ai/<package-name> start   # Run MCP server (stdio)
pnpm --filter @baichuan-ai/<package-name> start:sse     # Run in SSE mode (Cursor)
pnpm --filter @baichuan-ai/<package-name> start:http    # Run in Streamable HTTP mode
pnpm --filter @baichuan-ai/<package-name> start:hybrid  # Run in hybrid mode (recommended)

Publishing

pnpm changeset            # Create changeset for version bump
pnpm version-packages     # Update versions from changesets
pnpm release              # Build and publish to npm (runs scripts/publish.mjs --all)

Architecture

This is a pnpm workspace monorepo using Turborepo for build orchestration. All MCP servers are TypeScript ESM modules (ES2022 target, Node16 module resolution) under the @baichuan-ai/ npm scope.

Build Pipeline

Each package has a two-stage build:

1. UI bundle: Vite + vite-plugin-singlefile compiles HTML templates (e.g., src/ui/chat-result.html) into self-contained single-file HTML in dist/ui/
2. TypeScript: tsc compiles all .ts to dist/ with declarations and source maps

Package Layout

Within each MCP server package (packages/<name>/):

src/
├── index.ts          # Entry point: server init, transport selection, tool registration
├── tools/            # MCP tool definitions (zod schemas + handlers)
├── api/              # API client (HTTP fetch wrapper, types, error handling)
├── transport/        # Multi-protocol support (stdio, SSE, HTTP, hybrid)
└── ui/               # MCP Apps visual components (HTML templates, resources)