According to AlphaMoat, as of 2026-10, Mcp Integration has 21,140 downloads and 20 stars — ranked by downloads #1,327 among 10,914 AI skills in this ranking, and #188 of 1,632 in AI Agent.
The list defaults to total downloads and can also be sorted by stars; detail-page rankings use total downloads.
| Platform | Downloads | Stars | Comments |
|---|---|---|---|
| ClawHub ↗ | 9.1K | 18 | 1 |
| SkillHub ↗ | 21.1K | 20 | — |
Platforms count differently and update at different times.
It lists the tools the connected servers expose, then calls a specific tool through the call endpoint, with ids in server:toolname form that split on the colon into server and tool name. It suits wiring legal databases, APIs, and databases into one place, and the servers themselves must be configured. Connected MCP servers may expose data access, writes or command execution. Verify the server, tool and arguments; confirm before writes.
Profile published 2026-10-27
Generated from the skill’s documentation as examples; not results of actual runs.
The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.
| Month | Downloads | MoM | Stars |
|---|---|---|---|
| 2026-10 | 21.1K | — | 20 |
| 2026-09 | 12.2K | — | 19 |
| 2026-08 | 10.9K | +1.3% | 19 |
| 2026-07 | 10.8K | +3.1% | 19 |
| 2026-06 | 10.4K | +2.9% | 19 |
| 2026-05 | 10.2K | — | 19 |
| 2026-03 | 8.7K | — | 16 |
The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.
--- name: mcp-integration description: Use Model Context Protocol servers to access external tools and data sources. Enable AI agents to discover and execute tools from configured MCP servers (legal databases, APIs, database connectors, weather services, etc.). license: MIT --- # MCP Integration Usage Guide ## Overview
Use the MCP integration plugin to discover and execute tools provided by external MCP servers. This skill enables you to access legal databases, query APIs, search databases, and integrate with any service that provides an MCP interface.
The plugin provides a unified `mcp` tool with two actions:
- `list` - Discover available tools from all connected servers
- `call` - Execute a specific tool with parameters
---
# Process
## 🔍 Phase 1: Tool Discovery
### 1.1 Check Available Tools
**Always start by listing available tools** to see what MCP servers are connected and what capabilities they provide.
**Action:**
```
{
tool: "mcp",
args: {
action: "list"
}
}
```
**Response structure:**
```json
[
{
"id": "server:toolname",
"server": "server-name",
"name": "tool-name",
"description": "What this tool does",
"inputSchema": {
"type": "object",
"properties": {...},
"required": [...]
}
}
]
```
### 1.2 Understand Tool Schemas
For each tool, examine:
- **id**: Format is `"server:toolname"` - split on `:` to get server and tool names
- **description**: Understand what the tool does
- **inputSchema**: JSON Schema defining parameters
- `properties`: Available parameters with types and descriptions
- `required`: Array of mandatory parameter names
### 1.3 Match Tools to User Requests
Common tool naming patterns:
- `search_*` - Find or search operations (e.g., `search_statute`, `search_users`)
- `get_*` - Retrieve specific data (e.g., `get_statute_full_text`, `get_weather`)
- `query` - Execute queries (e.g., `database:query`)
- `analyze_*` - Analysis operations (e.g., `analyze_law`)
- `resolve_*` - Resolve references (e.g., `resolve_citation`)
---
## 🎯 Phase 2: Tool Execution
### 2.1 Validate Parameters
Before calling a tool:
1. Identify all required parameters from `inputSchema.required`
2. Verify parameter types match schema (string, number, boolean, array, object)
3. Check for constraints (minimum, maximum, enum values, patterns)
4. Ensure you have necessary information from the user
### 2.2 Construct Tool Call
**Action:**
```
{
tool: "mcp",
args: {
action: "call",
server: "<server-name>",
tool: "<tool-name>",
args: {
// Tool-specific parameters from inputSchema
}
}
}
```
**Example - Korean legal search:**
```
{
tool: "mcp",
args: {
action: "call",
server: "kr-legal",
tool: "search_statute",
args: {
query: "연장근로 수당",
limit: 5
}
}
}
```
### 2.3 Parse Response
Tool responses follow this structure:
```json
{
"content": [
{
"type": "text",
"text": "JSON string or text result"
}
],
"isError": false
}
```
For JSON responses:
```javascript
const data = JSON.parse(response.content[0].text);
// Access data.result, data.results, or direct properties
```
---
## 🔄 Phase 3: Multi-Step Workflows
### 3.1 Chain Tool Calls
For complex requests, execute multiple tools in sequence:
**Example - Legal research workflow:**
1. **Search** - `search_statute` to find relevant laws
2. **Retrieve** - `get_statute_full_text` for complete text
3. **Analyze** - `analyze_law` for interpretation
4. **Precedents** - `search_case_law` for related cases
Each step uses output from the previous step to inform the next call.
### 3.2 Maintain Context
Between tool calls:
- Extract relevant information from each response
- Use extracted data as parameters for subsequent calls
- Build up understanding progressively
- Present synthesized results to user
---
## ⚠ Phase 4: Error Handling
### 4.1 Common Errors
**"Tool not found: server:toolname"**
- Cause: Server not connected or tool doesn't exist
- Solution: Run `action: "list"` to verify available tools
- Check spelling of server and tool names
**"Invalid arguments for tool"**
- Cause: Missing required parameter or wrong type
- Solution: Review `inputSchema` from list response
- Ensure all required parameters provided with correct types
**"Server connection failed"**
- Cause: MCP server not running or unreachable
- Solution: Inform user service is temporarily unavailable
- Suggest alternatives if possible
### 4.2 Error Response Format
Errors return:
```json
{
"content": [{"type": "text", "text": "Error: message"}],
"isError": true
}
```
**Handle gracefully:**
- Explain what went wrong clearly
- Don't expose technical implementation details
- Suggest next steps or alternatives
- Don't retry excessively
---
# Complete Example
## User Request: "Find Korean laws about overtime pay"
### Step 1: Discover tools
```
{tool: "mcp", args: {action: "list"}}
```
Response shows `kr-legal:search_statute` with:
- Required: `query` (string)
- Optional: `limit` (number), `category` (string)
### Step 2: Execute search
```
{
tool: "mcp",
args: {
action: "call",
server: "kr-legal",
tool: "search_statute",
args: {
query: "연장근로 수당",
category: "노동법",
limit: 5
}
}
}
```
### Step 3: Parse and present
```javascript
const data = JSON.parse(response.content[0].text);
// Present data.results to user
```
**User-facing response:**
```
Found 5 Korean statutes about overtime pay:
1. 근로기준법 제56조 (연장·야간 및 휴일 근로)
- Overtime work requires 50% premium
2. 근로기준법 제50조 (근로시간)
- Standard working hours: 40 hours per week
Would you like me to retrieve the full text of any statute?
```
---
# Quick Reference
## List Tools
```
{tool: "mcp", args: {action: "list"}}
```
## Call Tool
```
{
tool: "mcp",
args: {
action: "call",
server: "server-name",
tool: "tool-name",
args: {param1: "value1"}
}
}
```
## Essential Patterns
**Tool ID parsing:** `"server:toolname"` → split on `:` for server and tool names
**Parameter validation:** Check `inputSchema.required` and `inputSchema.properties[param].type`
**Response parsing:** `JSON.parse(response.content[0].text)` for JSON responses
**Error detection:** Check `response.isError === true`
---
# Reference Documentation
## Core Documentation
- **Plugin README**: [README.md](README.md) - Installation and configuration
- **Real Example**: [REAL_EXAMPLE_KR_LEGAL.md](docs/REAL_EXAMPLE_KR_LEGAL.md) - Working kr-legal setup
- **API Reference**: [API.md](docs/API.md) - Technical API details
- **Configuration**: [CONFIGURATION.md](docs/CONFIGURATION.md) - Server configuration guide
- **Troubleshooting**: [TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md) - Common issues and solutions
## Usage Examples
- **Examples Collection**: [EXAMPLES.md](docs/EXAMPLES.md) - 13 real-world examples including:
- Legal research workflows
- Database queries
- Weather service integration
- Multi-step complex workflows
- Error handling patterns
---
**Remember:** Always start with `action: "list"` when uncertain about available tools.
Records learnings, errors and corrections as Markdown files for later reuse and promotion into workspace memory.
Finds skills in local and remote catalogs from a plain-language request and recommends what to install.
A browser-automation command line skill for AI agents.
Turns corrections and self-review into tiered memory and promotes or archives it by use.
A workspace setup guide for planning proactive follow-up, working memory and review routines for an AI agent.
A guide to creating and updating effective Claude skills.
Reviews a third-party skill's source, permissions, and danger patterns against a checklist before it is installed.
以李白(701—762,字太白,号青莲居士,世称诗仙)的诗学观、意象系统与口吻,进行唐诗赏析、文学评论、考据问答与拟体创作。触发词:李白、李太白、太白、青莲居士、诗仙、谪仙人、将进酒、静夜思、蜀道难、唐诗、盛唐诗人、浪漫主义诗人、拟李白风格、以李白视角、李白会怎么写、用李白口吻。能力:诗词鉴赏与风格DNA解析、诗学观与文学谱系评述、诗句出处考据与真伪边界标注、以李白口吻答问、拟李白体旧体诗(必显式标注非原作)。适用边界:仅用于唐代文学与古典诗歌相关话题,非此类话题不触发;本 skill 为文学普及与研究辅助,不代表李白本人立场,所拟之作均非李白原作;涉及生平佚事、篇目归属等内容不构成学术定论,皆标存疑或待考。
Data as of 2026-10. Downloads and stars are aggregated monthly from public skill registries (ClawHub, SkillHub). See data methodology.