mcp-development

Correlation ID tracing in MCP servers enables end-to-end request tracking across tool handlers. Use @sidequest/core/mcp to register tools with Zod schemas, implement correlation ID middleware in your handlers, and configure dual logging to both MCP protocol and local files for production observability.

Declarative tool registration uses Zod schemas and MCP annotations to define tool inputs, outputs, and metadata upfront. This pattern ensures type safety, self-documenting APIs, and compliance with the MCP protocol, eliminating manual handler boilerplate.

Yes. Bun is a supported runtime for production MCP servers. Implement file logging alongside MCP protocol logging using @sidequest/core/mcp patterns, and use spawnSyncCollect for wrapping CLI tools with structured output capture.

Structured error responses with recovery hints provide clear failure signals and debugging context. Log errors to both MCP protocol output and local files with correlation IDs to trace failures across the request lifecycle and identify root causes.

Before wrapping CLI tools, set up an MCP server with @sidequest/core/mcp, define Zod schemas for tool inputs and outputs, and implement spawnSyncCollect to capture and structure CLI output. Configure dual logging to track tool execution and errors.

Side Quest marketplace patterns enforce gold standard design for reliability and observability: declarative tool registration, structured error handling, correlation ID tracing, and dual logging. These patterns ensure servers meet production requirements and integrate seamlessly with the ecosystem.