SkillHub ClubShip Full StackFull StackBackendIntegration

analyze-mcp

Analyze MCP server structure and create wrapping strategy when user needs to understand an MCP server or create a CLI wrapper

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C0.0

Composite score

0.0

Best-practice grade

A88.0

Install command

npx @skill-hub/cli install brunogama-claude-mcp-wrapper-analyze-mcp

Repository

brunogama/claude-mcp-wrapper

Skill path: skills/analyze-mcp

Analyze MCP server structure and create wrapping strategy when user needs to understand an MCP server or create a CLI wrapper

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack, Backend, Integration.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: brunogama.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install analyze-mcp into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/brunogama/claude-mcp-wrapper before adding analyze-mcp to shared team environments
Use analyze-mcp for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: analyze-mcp
description: Analyze MCP server structure and create wrapping strategy when user needs to understand an MCP server or create a CLI wrapper
context: fork
agent: mcp-analyzer
allowed-tools:
  - Read
  - Bash
  - Grep
  - Glob
---

# Analyze MCP Server Structure

This skill analyzes an MCP server configuration and generates a comprehensive wrapping strategy.

## When This Skill Activates

Use this skill when:
- User asks about analyzing an MCP server
- User wants to understand MCP server capabilities
- User needs a wrapping strategy for an MCP server
- User requests tool inventory for an MCP
- Preparing to create a CLI wrapper

## What This Skill Does

1. Reads MCP server configuration from Claude Code
2. Introspects available tools and their signatures
3. Groups tools into logical namespaces
4. Designs 4-level progressive disclosure help structure
5. Recommends detail level enums for optimization
6. Estimates token savings potential
7. Generates implementation roadmap

## Usage

```
User: "Analyze the GitHub MCP server"
User: "What tools does the firecrawl MCP provide?"
User: "Create a wrapping strategy for the ref MCP"
```

## Output

Generates a comprehensive analysis report with:
- Tool inventory grouped by namespace
- Progressive disclosure structure (4 levels)
- Detail level recommendations
- Token efficiency estimates
- Implementation roadmap

## Example Output

```markdown
# MCP Server Analysis: github

## Server Overview
- Name: github
- Transport: stdio
- Tools Count: 15
- Configuration: ~/.config/claude/mcp.json

## Tool Inventory

### Namespace: repository
- **repository.get**: Get repository information
- **repository.list**: List user repositories
- **repository.create**: Create new repository

### Namespace: issue
- **issue.list**: List repository issues
- **issue.create**: Create new issue
- **issue.update**: Update issue

## Progressive Disclosure Structure
[4-level help outline]

## Token Efficiency Estimate
- Traditional approach: ~80,000 tokens per complex workflow
- Code API approach: ~5,000 tokens (93.8% savings)

## Implementation Roadmap
[Step-by-step plan]
```

## Agent Context

This skill runs in a forked context using the `mcp-analyzer` agent, which has specialized knowledge of:
- MCP protocol introspection
- Tool categorization patterns
- Progressive disclosure design
- Token efficiency optimization
- CLI wrapper patterns from ~/cli-wrappers/