MCP Tools Integration

Document MCP plugin usage patterns and map agents to recommended tools.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/komluk/scaffolding.template --skill mcp-tools-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Tools Integration
Source: https://github.com/komluk/scaffolding.template/tree/main/stacks/_common/.claude/skills/mcp-tools
Command: npx skills add https://github.com/komluk/scaffolding.template --skill mcp-tools-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines agent workflows by providing clear guidance on how to effectively integrate and utilize external tools through the Model Context Protocol (MCP).

Core Features & Use Cases

  • Tool Discovery: Understand how MCP plugins are named and accessed (mcp__pluginname__toolname).
  • Plugin Mapping: See which plugins are recommended for specific agents (e.g., playwright for developer, docker for devops).
  • Decision Tree: Follow a structured decision process to determine the appropriate MCP tool for a given task.
  • Use Case: An agent needs to debug a web application's UI. By consulting this skill, it identifies mcp__playwright__browser_navigate and mcp__playwright__browser_screenshot as the correct tools to use for reproducing and diagnosing the issue.

Quick Start

Use the mcp__docker__docker_ps tool to list running containers.

Frequently Asked Questions about MCP Tools Integration

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

FAQPage Schema
How do I integrate external tools like Playwright and Docker into my agent workflows?

You can integrate external tools into agent workflows using the Model Context Protocol (MCP). It provides a naming convention for plugins and maps specific agents to recommended tools for development and infrastructure tasks.

What is the Model Context Protocol (MCP) and how does it work with plugins?

The Model Context Protocol (MCP) is a system that facilitates integrating external tools into agents. Plugins are accessed using a specific naming convention, allowing agents to discover and utilize tools like ESLint and GitHub for various tasks.

How do I choose the right MCP plugin for a specific development or infrastructure task?

Choosing the right MCP plugin involves following a structured decision tree provided for tool selection. This process maps specific agents to recommended plugins, such as using Playwright for UI debugging or Docker for DevOps operations.

Can I use MCP plugins to automate web application UI debugging?

Yes, you can use MCP plugins to automate web application UI debugging. By consulting the plugin mapping, agents identify tools like browser navigation and screenshot capabilities to reproduce and diagnose interface issues.

Does MCP integration require specific dependencies to manage running containers?

Managing running containers via MCP does not require specific external dependencies. You can directly use the integrated Docker plugin commands to list containers and handle infrastructure tasks within your agent workflows.

What are the limitations of using MCP plugins for workflow automation?

Limitations of using MCP plugins for workflow automation include adhering to mandatory usage rules and structured decision trees. Agents must correctly identify tools using the specific naming convention to avoid integration errors with external services.