add-dto

Standardize request and response DTO definitions for MCP server endpoints.

11|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill add-dto-artk0de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-dto
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude/skills/add-dto
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill add-dto-artk0de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the inconsistency and technical debt associated with defining request and response shapes for MCP endpoints by providing a structured, domain-driven approach to DTO management.

Core Features & Use Cases

  • Domain-Driven Organization: Groups DTOs by functional domain (explore, ingest, collection, document) to maintain a clean API surface.
  • Standardized Interface Patterns: Enforces naming conventions and inheritance rules for request and response types.
  • Use Case: When adding a new search feature to the MCP server, use this skill to define the required request and response interfaces in the appropriate domain file and ensure they are correctly exported through the barrel files.

Quick Start

Use the add-dto skill to create a new request and response type for the collection domain following the established interface patterns.

Frequently Asked Questions about add-dto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Data Transfer Objects for MCP server endpoints in TypeScript?

To standardize Data Transfer Objects for MCP server endpoints, you group request and response interfaces by functional domain using barrel exports to ensure type safety and architectural consistency across the public API surface.

What is the best way to organize DTO interfaces for an MCP API surface?

Organizing DTO interfaces for an MCP API surface requires a domain-driven approach, grouping types by functional domains like explore, ingest, collection, and document to maintain a clean and consistent API structure.

How do I define request and response types for a new MCP server feature?

Defining request and response types for a new MCP server feature involves adding interfaces to the appropriate domain file and ensuring they are correctly exported through established barrel export patterns for integration.

Why does my MCP server have architectural inconsistency with public API data shapes?

Architectural inconsistency with public API data shapes arises from unstructured DTO definitions, which can be resolved by enforcing standardized interface patterns, naming conventions, and inheritance rules for request and response types.

Do I need barrel exports to manage TypeScript DTOs for an MCP server?

Yes, barrel exports are required to manage TypeScript DTOs for an MCP server, ensuring that newly defined domain-specific request and response interfaces are correctly integrated and exported within existing contracts.