Agent skill · software engineering · aiskillstore
mcp-apps-builder
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP development or mcp-use patterns - Making ANY changes to server.tool(), server.resource(), server.prompt(), or widgets This skill contains critical architecture decisions, security patterns, and common pitfalls. Always consult the relevant reference files BEFORE implementing MCP features.
Why this skill is useful
Provides detailed architecture patterns and security best practices for building MCP servers that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
IMPORTANT: How to Use This Skill This file provides a NAVIGATION GUIDE ONLY. Before implementing any MCP server features, you MUST: 1. Read this overview to understand which reference files are relevant 2. ALWAYS read the specific reference file(s) for the features you're implementing 3. Apply the detailed patterns from those files to your implementation Do NOT rely solely on the quick reference examples in this file - they are minimal examples only. The reference files contain critical best practices, security considerations, and advanced patterns. --- MCP Server Best Practices Comprehensive guide for building production-ready MCP servers with tools, resources, prompts, and widgets using mcp-use. ⚠️ FIRST: New Project or Existing Project? Before doing anything else, determine whether you are inside an existing mcp-use project. Detection: Check the workspace for a package.json that lists "mcp-use" as a dependency, OR any .ts file that imports from "mcp-use/server". NEVER manually create MCPServer boilerplate, package.json, or project structure by hand. The CLI sets up TypeScript config, dev scripts, inspector integration, hot reload, and widget compilation that are difficult to replicate manually. --- Scaffolding a New Project For full scaffolding details and CLI flags, see quickstart.md. --- Quick Navigation Choose your path based on what you're building: 🚀 Foundations When: ALWAYS read these first when starting MCP work in a new conversation. Reference later for architecture/concept clarification. 1. concepts.md - MCP primitives (Tool, Resource, Prompt, Widget) and when to use each 2. architecture.md - Server structure (Hono-based), middleware system, server.use() vs server.app 3. quickstart.md - Scaffolding, setup, and first tool example 4. deployment.md - Deploying to Manufact Cloud, self-hosting, Docker, managing deployments Load these before diving into tools/resources/widgets sections. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/mcp-apps-builder--07902f