Monorepo Build System With Pnpm And Automated Sdk Publishing

via “monorepo package architecture with shared utilities and platform abstraction”

Manage Supabase databases, auth, and storage via MCP.

Unique: Separates platform abstraction layer from tool implementations using monorepo architecture, enabling independent evolution of transport mechanisms and tool capabilities. Provides shared utilities package (@supabase/mcp-utils) that other MCP servers can depend on, creating ecosystem of compatible servers.

vs others: Monorepo with shared utilities reduces code duplication and enables consistent tool implementations across distribution channels, whereas separate repositories would require duplicating transport logic and maintaining version compatibility manually.

via “pnpm workspace dependency management with workspace protocol”

T3 stack monorepo with Next.js, Expo, tRPC, and Drizzle.

Unique: Uses pnpm's workspace:* protocol to create symlinks to local packages during development, enabling zero-latency feedback on changes across @acme/* packages, while automatically converting to concrete versions during npm publish without manual version bumping

vs others: Faster than npm/yarn workspaces for local development because workspace:* creates symlinks rather than copying packages, and more reliable than Lerna because pnpm's strict dependency resolution prevents phantom dependencies that break in production

via “monorepo-build-system-with-incremental-compilation”

Open-source, self-hosted CMS platform on AWS serverless (Lambda, DynamoDB, S3). TypeScript framework with multi-tenancy, lifecycle hooks, GraphQL API, and AI-assisted development via MCP server. Built for developers at large organizations.

Unique: Uses Rspack (Rust-based bundler) with custom incremental compilation logic that tracks package dependencies and only rebuilds affected packages, combined with tree-shaking to minimize Lambda function bundle sizes

vs others: Provides incremental compilation and caching for large monorepos with Rspack bundling, whereas Lerna/Nx require separate configuration and Turborepo has less fine-grained control over bundling

via “monorepo-based development with pnpm workspaces and shared packages”

The open-source hub to build & deploy GPT/LLM Agents ⚡️

Unique: Uses pnpm workspaces to manage 12 core packages, 50+ integrations, and plugins in a single repository with shared dependencies and consistent versioning, enabling atomic cross-package changes

vs others: More efficient than separate repositories for managing integrations; pnpm's strict dependency resolution prevents version conflicts that plague npm-based monorepos

via “monorepo structure with pnpm and turborepo for dependency management”

Streaming music player that finds free music for you

Unique: Uses pnpm workspaces with Turborepo for intelligent build caching and parallel execution, reducing build times by 40-60% compared to sequential builds. The monorepo structure enables the plugin SDK to be published independently, allowing third-party developers to build plugins without waiting for core player releases.

vs others: More efficient than separate repositories because shared dependencies are deduplicated; faster builds than Lerna because Turborepo uses content-based caching; more maintainable than single-package repos because concerns are clearly separated.

via “monorepo structure with turborepo build orchestration”

AI PDF chatbot agent built with LangChain & LangGraph

Unique: Uses Turborepo to orchestrate builds across multiple workspaces with intelligent caching, avoiding redundant builds when packages haven't changed. Shared types package enables type-safe communication between frontend and backend.

vs others: Faster builds than separate repositories because Turborepo caches unchanged packages; easier type sharing than separate repos because types live in a shared package.

Open-source, secure environment with real-world tools for enterprise-grade agents.

Unique: pnpm workspace with shared build configuration reduces duplication across JS/Python SDKs; automated CI/CD publishing to multiple registries (npm, PyPI) eliminates manual release steps vs separate repositories

vs others: More maintainable than separate repositories because shared dependencies and tooling reduce drift; faster builds than npm/yarn because pnpm uses hard links for dependency deduplication

via “monorepo architecture with shared utilities and independent server packages”

** - Connects to Supabase platform for database, auth, edge functions and more.

via “monorepo structure support with build pipeline and release management”

The best agent harness.

Unique: Implements monorepo support with a TypeScript-based build pipeline and coordinated release management via migration manifests and version tracking. The system enables coordinated builds and releases across multiple packages.

vs others: Unlike generic monorepo tools (Lerna, Nx), Trellis monorepo support is integrated with the Trellis framework and enables coordinated AI-assisted development across packages. Unlike manual release processes, the build pipeline and versioning system automate coordination.

via “monorepo structure with shared packages and extension modules”

Open-Source Chrome extension for AI-powered web automation. Run multi-agent workflows using your own LLM API key. Alternative to OpenAI Operator.

Unique: Uses pnpm workspaces to organize the extension as a monorepo with separate packages for storage, utilities, and the extension itself. This enables code reuse and independent testing while maintaining a single build pipeline. The storage package is particularly reusable — it can be imported by other extensions or tools.

vs others: More maintainable than a single-file extension because modules are decoupled, and more flexible than a multi-repo approach because dependencies are managed centrally and code sharing is straightforward.

via “monorepo structure with pnpm workspaces”

The TypeScript MCP framework

Unique: Uses pnpm workspaces to organize the xmcp project as a monorepo with separate packages for the core framework, CLI tools, plugins, documentation, and examples. This enables independent versioning and publishing while maintaining shared dependencies and coordinated development.

vs others: More efficient than separate repositories because pnpm deduplicates dependencies and enables atomic commits across packages. More maintainable than a single package because each component can be versioned and published independently.

via “monorepo structure with independent server versioning and pypi publishing”

Neo4j Labs Model Context Protocol servers

Unique: Implements a monorepo structure where each of four servers is independently versioned and published to PyPI, allowing selective deployment and independent release cycles while sharing common infrastructure and patterns. Uses uv.lock for reproducible dependency management across servers.

vs others: Monorepo with independent versioning enables selective deployment and independent release cycles, whereas separate repositories would require manual coordination; monorepo approach provides shared patterns while maintaining deployment flexibility.

via “monorepo build orchestration with sequential package dependency resolution”

HyperChat is a Chat client that strives for openness, utilizing APIs from various LLMs to achieve the best Chat experience, as well as implementing productivity tools through the MCP protocol.

Unique: Implements a monorepo structure with sequential build orchestration and shared type foundation, enabling multiple interfaces (CLI, Web, Electron) to share identical backend services while maintaining clean dependency separation

vs others: Unlike separate repositories (which require manual synchronization) or tightly-coupled monoliths (which lack modularity), HyperChat's monorepo provides shared backend logic with independent interface deployment options

via “monorepo development framework with pnpm workspaces and turbo”

MCP server for interacting with Cloudflare API

Unique: Uses pnpm workspaces and Turbo to manage 15+ independent MCP servers in a single monorepo, enabling efficient builds and deployments through shared configuration and incremental compilation; provides scaffolding for new servers.

vs others: More efficient than separate repositories because it enables code sharing, consistent tooling, and parallel builds; more maintainable than manual build scripts because Turbo handles dependency ordering and caching automatically.

via “monorepo architecture with turborepo caching and pnpm workspaces”

** - Make your AI agent speak every language on the planet, using [Lingo.dev](https://lingo.dev) Localization Engine.

Unique: Uses a layered monorepo architecture where foundational packages (@lingo.dev/_locales, @lingo.dev/_spec) have zero internal dependencies, enabling independent development and testing, combined with Turborepo caching for fast incremental builds across 5+ interdependent packages.

vs others: More efficient than separate repositories for managing related packages; Turborepo caching provides faster builds than npm/yarn workspaces alone, enabling rapid iteration on the full Lingo.dev stack.

via “monorepo workspace dependency management and build orchestration”

** - Interact with [Twilio](https://www.twilio.com/en-us) APIs to send messages, manage phone numbers, configure your account, and more.

Unique: Uses npm workspaces with a prepare script to enforce build ordering (generic package before Twilio package), ensuring the dependency chain is respected without requiring manual build commands

vs others: Provides automatic build orchestration via npm workspaces rather than requiring manual build scripts or external tools like Lerna, reducing complexity for maintaining multiple related packages

via “monorepo-optimized tool service composition and sharing”

A NestJS library for building transport-agnostic MCP tool services. Define tools once with decorators, consume them over HTTP, stdio, or directly via the registry. The documentation and examples generally focus one enterprise monorepos but can be easily a

Unique: Leverages NestJS's module system to enable tool sharing across monorepo services without code duplication, treating tools as first-class NestJS modules — most MCP libraries are designed for single-service deployment and don't address monorepo composition patterns

vs others: Eliminates tool definition duplication across services compared to per-service tool implementations, and enables consistent tool behavior across the monorepo

via “typescript monorepo with turborepo build orchestration”

An alternative to Supabase for AI Code editors and Vibe Coding tools