ereminmaksim/mcp-by-doca-mayao

Purpose and Interfaces

This is a read-only Model Context Protocol (MCP) server exposing MAYAO component documentation and onboarding guidance from bundled JSON data. It supports both networked MCP over HTTP and local MCP over stdio. Main entry points are src/server.ts (HTTP) and src/stdio.ts (stdio transport).

Transport and Session Boundary

The HTTP adapter serves health, metrics, and MCP endpoints; MCP clients initialize a JSON-RPC session, then pass mcp-session-id on subsequent requests. The stdio adapter exposes the same tool capability without HTTP/session-origin concerns.

• src/http.ts

• src/server.ts

• src/stdio.ts

MCP Tool Surface

Tool modules define the public read-only operations: list, retrieve, search, recommend, and compare components, plus retrieve/search onboarding content. These are the protocol-facing orchestration layer that validates inputs and delegates to services.

• src/tools/listComponents.ts

• src/tools/compareComponents.ts

• src/tools/searchDocs.ts

Domain Services and Search Flow

Services implement domain queries over the static catalog: component lookup/listing, onboarding lookup, and cross-document search. Recommendation and comparison tools compose this service-level data rather than calling an external documentation system.

• src/services/components.ts

• src/services/onboarding.ts

• src/services/search.ts

Source-of-Truth Data and Transformation

The repository embeds its documentation catalog as JSON. Transform modules convert raw data records into the shapes expected by services and MCP tool responses, creating a boundary between stored content and protocol/domain models.

• src/data/componentsData.json

• src/data/onboardingData.json

• src/transforms/componentTransform.ts

• src/transforms/onboardingTransform.ts

Schema and Validation Boundary

Shared and domain-specific schemas constrain component and onboarding request/data structures before tool or service processing. This keeps malformed MCP arguments from reaching data-query logic.

• src/schemas/common.ts

• src/schemas/component.ts

• src/schemas/onboarding.ts

Security, Operations, and Deployment

The HTTP runtime applies request-size limits, IP rate limiting, origin allow-listing, session TTL cleanup, concurrency/timeout/circuit-breaker controls, audit logging, and rolling metrics. Runtime configuration is environment-driven; Railway/Nixpacks deployment files indicate a Node/TypeScript service deployment with no database or external content API.

• src/security.ts

• src/config.ts

• railway.json

• nixpacks.toml