# mcp-tool-docs-stinger

mcp-tool-docs-stinger — a skill for documenting MCP tools, TypeScript APIs, and CLIs grounded in source code: schemas, outputs, side effects, examples. Use when writing or auditing tool, API, or CLI documentation.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/documentation-tools/skills/mcp-tool-docs-stinger/SKILL.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/mcp-tool-docs-stinger

## What it does

mcp-tool-docs-stinger teaches how to document MCP tool schemas honestly—straight from the tool registration and handler code. It covers how to describe inputs and outputs, side effects, annotations, and usage examples. The skill also addresses TypeScript API references (using TypeDoc or API Extractor), CLI command surfaces, and keeping documentation in sync with code to prevent drift.

The skill includes step-by-step guides in `guides/` (documentation principles, how-to for each surface type, a 10-point validation checklist), templates in `templates/`, and worked examples based on Hivemind—an MCP server with a TypeScript API and CLI. Start by reading `guides/00-principles.md`, then `guides/01-mcp-tool-docs.md`, then proceed by task.

For Claude Code, install via the plugin marketplace. Codex, Cursor, and other platforms have alternative installation methods.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install documentation-tools@wasp-nest
```
This installs the whole documentation-tools plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-tool-docs-stinger -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/mcp-tool-docs-stinger/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/mcp-tool-docs-stinger/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-tool-docs-stinger -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/mcp-tool-docs-stinger/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-tool-docs-stinger -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/mcp-tool-docs-stinger/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install legioncodeinc/vibe-coding-tools plugins/documentation-tools/skills/mcp-tool-docs-stinger
```

2. **Manually: put the files in place**
- File: `.github/skills/mcp-tool-docs-stinger/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-tool-docs-stinger -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/documentation-tools/skills/mcp-tool-docs-stinger
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/mcp-tool-docs-stinger/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/documentation-tools/skills/mcp-tool-docs-stinger/SKILL.md

## When to use it
- Write input and output schemas for an MCP tool that stays true to the code
- Generate a TypeScript API reference from source
- Document CLI commands, flags, and their side effects
- Find where documentation has drifted from the code
- Write a changelog entry tied to a released version

## Example prompts
- Document these MCP tools with honest schema and output descriptions
- Is this tool description accurate? Does it match what the code does?
- Resync the documentation—it's out of step with the code

## Similar
- [project-docs](https://affpapa.org/en/nevibecode/skills/project-docs.md) — skill · 1300 installs
- [jsdoc-typescript-docs](https://affpapa.org/en/nevibecode/skills/jsdoc-typescript-docs.md) — skill · 572 installs
- [coralogix-docs](https://affpapa.org/en/nevibecode/skills/coralogix-docs.md) — skill · 5000 installs
- [api-docs](https://affpapa.org/en/nevibecode/skills/api-docs.md) — skill · 893 installs
- [stream-docs](https://affpapa.org/en/nevibecode/skills/stream-docs.md) — skill · 856 installs
- [reading-livekit-docs](https://affpapa.org/en/nevibecode/skills/reading-livekit-docs.md) — skill · 561 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
