skills.rest
XAIHT
XAIHTOFFICIAL
Explore all skills by this author →
Website𝕏@XAIHT2026GitHub

create-new-mcp

Document the procedure for adding tools and MCP context providers to Tlamatini.

14|1|Updated Mar 6, 2026
Search Tags:#workflow#development#documentation#integration#mcp#tool
One-click install
npx skills add https://github.com/XAIHT/Tlamatini --skill create-new-mcp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-new-mcp
Source: https://github.com/XAIHT/Tlamatini/tree/main/Tlamatini/agent/skills_pkg/create_new_mcp
Command: npx skills add https://github.com/XAIHT/Tlamatini --skill create-new-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The authoritative reference for adding a new tool, MCP context provider, or both to Tlamatini. It clarifies when and how to register a tool, create MCP servers/clients, seed migrations, extend factory, and adjust frontend checkboxes.

Core Features & Use Cases

  • Canonical reference for tool and MCP integration
  • Clear decision framework to classify requests as tool-only, MCP-backed context provider, or both
  • Step-by-step guidance on required files, migrations, and frontend updates to ensure safe, correct integration

Quick Start

Read the canonical guide at Tlamatini/.mcps/create_new_mcp.md to begin.

Frequently Asked Questions about create-new-mcp

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

FAQPage Schema
How do I add a new MCP context provider to my development workflow?▼

To add an MCP context provider, follow the canonical guide detailing required file changes, MCP server or client creation, migration seeding, and factory extensions to ensure safe integration.

What is the difference between registering a standalone tool and an MCP-backed context provider?▼

A standalone tool requires standard registration, while an MCP-backed context provider involves creating MCP servers or clients and seeding migrations, with a decision framework to classify requests as tool-only, MCP-backed, or both.

What files and migrations do I need to modify for a new tool integration?▼

New tool integration requires modifying specific files, seeding database migrations, extending the factory, and adjusting frontend checkboxes, following strict naming conventions and sequencing for correct integration.

Do I need to update frontend checkboxes when adding an MCP server?▼

Yes, adjusting frontend checkboxes is a required step when adding an MCP server or context provider, ensuring the new integration is correctly exposed and managed within the user interface.

What guardrails and permissions are required for safe MCP integration?▼

Safe MCP integration requires adhering to specified guardrails, permissions, and sequencing, ensuring that tool registration and context provider creation follow strict security and operational rules.

When should I not use a standalone tool versus an MCP context provider?▼

Use the decision framework to classify requests; if the requirement only needs a simple tool, register it standalone, but if it demands contextual data integration, create an MCP server or client instead.

Related Skills

Explore More Software Engineering Skills→
cookercooker
66

using-git-worktrees

Create isolated Git worktrees with automated setup and baseline verification.

Community
Intermediate
birgitta410birgitta410
15

_local-setup

Automate local installation and configuration of the sensors-cli development environment.

Community
Basic
zeronx798zeronx798

mcporter

Manage MCP servers and tools via a command-line interface.

Community
Intermediate
modelcontextprotocolmodelcontextprotocol
2.7k

convert-web-app

Add MCP App support to existing web applications with hybrid initialization and resource registration.

Official
Intermediate