mcp-create

Scaffold and register new MCP tools with Rust handlers and ontology updates.

19|3|Updated Jul 19, 2024
One-click install
npx skills add https://github.com/danielterra/FOUNDATION --skill mcp-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-create
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/mcp-create
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill mcp-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided workflow to scaffold and register new Foundation MCP tools, ensuring consistent Rust handlers, tool templates, and ontology entries.

Core Features & Use Cases

  • Automates the creation of a new MCP tool by generating the Rust handler, wiring the runtime dispatch, and creating the foundation:MCPTool ontology individual.
  • Validates metadata and stepwise integration with the MCP server to prevent duplicates and ensure reloading works.
  • Use Case: When a developer needs to extend Foundation with a new MCP tool to expose a JSON-RPC surface and an ontology contract.

Quick Start

Create a new MCP tool by implementing its Rust handler, registering the ToolTemplate, wiring the dispatch, and adding the foundation:MCPTool entry in the ontology.

Frequently Asked Questions about mcp-create

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

FAQPage Schema
How do I create a new MCP tool and register it in Foundation?

To create a new MCP tool, this Skill automates generating the Rust handler, wiring the runtime dispatch, and creating the foundation:MCPTool ontology individual. It validates metadata and integration to ensure reloading works.

What is an MCP tool ontology entry and when do I need one?

An MCP tool ontology entry is a foundation:MCPTool individual defining the contract for a JSON-RPC surface. You need one when extending Foundation with a new MCP tool to ensure consistent integration and valid metadata.

How does MCP server dispatch wiring work for a new Rust handler?

MCP server dispatch wiring connects the generated Rust handler to the runtime dispatch via a registered ToolTemplate. This ensures the new MCP tool is properly routed and exposed on the JSON-RPC surface.

Can I use this to scaffold MCP tools without writing boilerplate Rust code?

Yes, this Skill scaffolds the Rust handler and tool-template wiring automatically. It applies to tool development workflows requiring consistent MCP integration, handling validation, compilation, and reloading steps end-to-end.

Why does my MCP tool creation fail validation or reloading?

MCP tool creation fails when metadata is invalid or stepwise integration with the MCP server is incomplete. This Skill prevents duplicates and ensures reloading works by validating metadata throughout the scaffolding process.

Does this MCP tool scaffolding workflow prevent duplicate ontology registrations?

Yes, this Skill validates metadata and stepwise integration with the MCP server to prevent duplicates. It ensures the foundation:MCPTool ontology individual is registered correctly and reloading works without conflicts.