endpoint-creation

Define reusable endpoint patterns abstracting business logic from HTTP and MCP plumbing.

Updated Jan 11, 2026

Search Tags:#testing #openapi #zod #mcp #http #endpoint #hono

Ready to run

npx skills add https://github.com/GeorgeSheppard/api.georgesheppard.dev --skill endpoint-creation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: endpoint-creation
Source: https://github.com/GeorgeSheppard/api.georgesheppard.dev/tree/main/.claude/skills/endpoint-creation
Command: npx skills add https://github.com/GeorgeSheppard/api.georgesheppard.dev --skill endpoint-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and maintaining consistent endpoints across HTTP and MCP interfaces is error-prone and duplicative. This skill provides a standardized pattern to build reusable endpoint components (handler, validator, and route definition) that work in both HTTP and MCP contexts, reducing duplication and improving maintainability.

Core Features & Use Cases

Reusable core: Handlers are decoupled from HTTP/MCP specifics, enabling cross-interface usage.
Clear structure: Each endpoint has a dedicated directory with a consistent layout (handler, route-definition, tests).
OpenAPI-ready: Route definitions integrate with OpenAPI and validation schemas for reliable API documentation.
Testable: Pure business logic that can be tested without HTTP context.

Quick Start

Register a new endpoint following the standard directory layout and hook it into the main app to enable both HTTP and MCP routes.

Frequently Asked Questions about endpoint-creation

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

FAQPage Schema

How do I create reusable endpoints that work for both HTTP and MCP servers?▼

Reusable endpoints abstract business logic from HTTP and MCP plumbing, allowing the same handler to be reused across interfaces. This pattern applies within a Hono-based stack using a consistent folder structure for each route.

How do I validate Hono endpoints with Zod and generate OpenAPI definitions?▼

Endpoints satisfy type-safe contracts by integrating Zod schemas with OpenAPI route definitions. This combination ensures reliable API documentation and automatic validation for HTTP requests within the Hono framework.

What is the best way to test Hono endpoint business logic without an HTTP context?▼

Testing endpoint business logic without HTTP context is achieved by decoupling handlers from HTTP and MCP specifics. Pure handler functions can be tested directly using modular route definitions and validation schemas.

Can I use the same handler for an HTTP route and an MCP tool in Hono?▼

Yes, the same handler can be used for both HTTP routes and MCP tools. The endpoint pattern decouples core logic from transport-specific plumbing, enabling cross-interface usage without duplicating code.

What folder structure should I use for Hono API endpoints to maintain consistency?▼

Each endpoint should have a dedicated directory with a consistent layout containing the handler, route definition, and tests. This modular structure hooks into the main app to enable both HTTP and MCP routes.