@zerobuild/mcp-core

Provides a centralized registry for defining and managing MCP tools with JSON Schema validation. Tools are registered with name, description, input schema, and handler functions, enabling both the hosted Zerobuild server and stdio transport clients to discover and invoke tools through a unified interface without duplicating tool definitions across multiple transport implementations.

Manages MCP resources (documents, files, data sources) with URI-based addressing and content serving. Resources are registered with URI templates, MIME types, and content providers, allowing clients to request resources by URI and receive content with proper type information. Supports both static resources and dynamic content generation through provider functions.

Registers reusable prompt templates with parameter placeholders and metadata, enabling LLM clients to discover and invoke parameterized prompts. Templates support variable substitution, argument validation, and optional descriptions for each parameter. Prompts are registered once and made available across all MCP transport implementations without duplication.

Provides a unified API for registering tools, resources, and prompts that works transparently across both the hosted Zerobuild server and stdio transport implementations. The same registration calls populate both transport layers, eliminating the need to maintain separate registration logic for each transport mode. Uses dependency injection or factory patterns to adapt registrations to transport-specific requirements.

Provides TypeScript interfaces and type definitions for tools, resources, and prompts, enabling compile-time type checking of tool schemas, handler function signatures, and parameter types. Tool handlers are typed to match their input schemas, and resource providers are typed to return correct content types. Uses TypeScript generics to enforce type safety across the registration and invocation pipeline.