skills.rest
artk0de
artk0deCOMMUNITY
Explore all skills by this author →
GitHub

add-mcp-endpoint

Create and register MCP tools following TeaRAGs-MCP DTO, facade, and registration patterns.

11|3|Updated Jan 29, 2026
Search Tags:#typescript#architecture#api#backend#tooling#mcp
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill add-mcp-endpoint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-mcp-endpoint
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude/skills/add-mcp-endpoint
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill add-mcp-endpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction and inconsistency of manually wiring new MCP tools by providing a strict, multi-phase implementation checklist that ensures architectural integrity and protocol compliance.

Core Features & Use Cases

  • Coordinated Implementation: Guides the user through the entire lifecycle of an endpoint, from DTO definition to Zod schema registration and documentation.
  • Architectural Guardrails: Enforces the separation of concerns between the API facade, internal operations, and MCP tool registration.
  • Use Case: When you need to expose a new search strategy or data mutation as an MCP tool, follow this workflow to ensure the code is testable, documented, and properly integrated into the TeaRAGs architecture.

Quick Start

Use the add-mcp-endpoint skill to guide the implementation of a new tool for querying codebase ownership metrics.

Frequently Asked Questions about add-mcp-endpoint

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

FAQPage Schema
How do I register a new MCP tool without breaking existing API architecture?▼

Standardizing MCP tool creation requires following a strict implementation checklist that defines DTOs, applies facade patterns, and registers Zod schemas to maintain architectural integrity and protocol compliance.

What is the correct workflow for exposing an internal operation as an MCP tool in a TypeScript backend?▼

Exposing an internal operation as an MCP tool requires a coordinated workflow from DTO definition to Zod schema registration and documentation, ensuring the new endpoint is testable and properly integrated into the TeaRAGs architecture.

Do I need to use Zod schemas when adding MCP endpoints to my backend?▼

Yes, using Zod schemas is required when adding MCP endpoints to standardize tool creation, ensure protocol compliance, and maintain system consistency throughout the API facade and registration patterns.

Why does manually wiring new MCP tools cause architectural inconsistencies?▼

Manually wiring new MCP tools causes architectural inconsistencies because it lacks strict separation of concerns between the API facade, internal operations, and tool registration, leading to friction and protocol non-compliance.

Can I use this MCP tool registration workflow for data mutations and search strategies?▼

Yes, this workflow applies to exposing both new search strategies and data mutations as MCP tools, ensuring that any new API endpoint is properly documented, testable, and integrated into the existing architecture.

Related Skills

Explore More Software Engineering Skills→
anicdhanicdh

typescript-nestjs

Codify NestJS backend patterns for scalable APIs with TypeScript, Prisma, and PostgreSQL.

Community
Advanced
jhlee0409jhlee0409
4

openapi-parser

Parse OpenAPI 3.x and Swagger 2.0 specs into structured endpoint catalogs.

Community
Advanced
windyskywindysky

moai-platform-convex

Build Convex-based real-time backends with TypeScript, reactive queries, and Clerk/Auth0.

Community
Advanced
alibabaalibaba
2.2k

riper5-protocol

Guide complex software engineering tasks with strict protocol compliance and risk mitigation.

Official
Advanced