Files
leo-claude-mktplace/plugins/debug-mcp/commands/debug-mcp-inspect.md
lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-06 14:52:11 -05:00

130 lines
3.1 KiB
Markdown

---
name: debug-mcp inspect
description: Inspect MCP server configuration, dependencies, and tool definitions
---
# /debug-mcp inspect
Deep inspection of an MCP server's configuration, dependencies, and tool definitions.
## Skills to Load
- `skills/visual-header.md`
- `skills/venv-diagnostics.md`
- `skills/mcp-protocol.md`
## Agent
Delegate to `agents/mcp-debugger.md`.
## Usage
```
/debug-mcp inspect <server_name> [--tools] [--deps] [--config]
```
**Arguments:**
- `server_name` - Name of the MCP server from .mcp.json
**Options:**
- `--tools` - List all registered tools with their schemas
- `--deps` - Show dependency analysis (installed vs required)
- `--config` - Show configuration files and environment variables
- (no flags) - Show all sections
## Instructions
Execute `skills/visual-header.md` with context "Server Inspection".
### Phase 1: Configuration
1. Read `.mcp.json` and extract the server definition
2. Display:
- Server name
- Command and arguments
- Working directory
- Environment variable references
```
## Server: gitea
### Configuration (.mcp.json)
- Command: /path/to/mcp-servers/gitea/.venv/bin/python
- Args: ["-m", "mcp_server.server"]
- CWD: /path/to/mcp-servers/gitea
- Env file: ~/.config/claude/gitea.env
```
### Phase 2: Dependencies (--deps)
Apply `skills/venv-diagnostics.md`:
1. Read `requirements.txt` from the server's cwd
2. Compare with installed packages:
```bash
cd <cwd> && .venv/bin/pip freeze
```
3. Identify:
- Missing packages (in requirements but not installed)
- Version mismatches (installed version differs from required)
- Extra packages (installed but not in requirements)
```
### Dependencies
| Package | Required | Installed | Status |
|---------|----------|-----------|--------|
| mcp | >=1.0.0 | 1.2.3 | OK |
| httpx | >=0.24 | 0.25.0 | OK |
| pynetbox | >=7.0 | — | MISSING |
- Missing: 1 package
- Mismatched: 0 packages
```
### Phase 3: Tools (--tools)
Parse the server source code to extract tool definitions:
1. Find Python files with `@mcp.tool` decorators or `server.add_tool()` calls
2. Extract tool name, description, and parameter schema
3. Group by module/category if applicable
```
### Tools (42 registered)
#### Issues (6 tools)
| Tool | Description | Params |
|------|-------------|--------|
| list_issues | List issues from repository | state?, labels?, repo? |
| get_issue | Get specific issue | issue_number (required) |
| create_issue | Create new issue | title (required), body (required) |
...
```
### Phase 4: Environment Configuration (--config)
1. Locate env file referenced in .mcp.json
2. Read the file (mask secret values)
3. Check for missing required variables
```
### Environment Configuration
File: ~/.config/claude/gitea.env
| Variable | Value | Status |
|----------|-------|--------|
| GITEA_API_URL | https://gitea.example.com/api/v1 | OK |
| GITEA_API_TOKEN | ****...a1b2 | OK |
File: .env (project level)
| Variable | Value | Status |
|----------|-------|--------|
| GITEA_ORG | personal-projects | OK |
| GITEA_REPO | leo-claude-mktplace | OK |
```
## User Request
$ARGUMENTS