monorepo-package-workflow

Create a new MCP tool package by generating a modular structure under packages/your-tool/ with src/{constants,helpers,utils}, a thin mcp-server.ts (<150 LOC), package.json, tsconfig, and tools.json registration. Implement core logic following ES module syntax and <300 LOC per file constraints, then run npm run version:sync to synchronize versions.

An MCP server file should be thin and focused, staying under 150 lines of code with proper extension handling (.js output) and ES module syntax. Core logic belongs in modular src/{constants,helpers,utils} files to keep the server file lean and maintainable.

Add your package entry to tools.json with proper version references, then run npm run version:sync to automatically synchronize versions across the monorepo. This ensures consistent versioning and standardized registration of your MCP tool.

MCP packages must maintain test coverage above 70% with validated import patterns and registration tests. Tests should verify that your package integrates correctly with the monorepo's standardized structure and tools.json registration.

This Skill provides scaffolding patterns specifically designed for the @j0kz/mcp-agents monorepo. The standardized structure, version-sync workflow, and tools.json integration are tailored to that ecosystem's requirements.

MCP packages enforce <300 LOC per file, <150 LOC for mcp-server.ts, modular src/ organization (constants, helpers, utils), and proper .js extension handling. These constraints ensure consistency, maintainability, and thin server architecture across packages.