# mcp-tool-docs-wasp-drone

mcp-tool-docs-wasp-drone is a Claude Code subagent for documenting MCP tools, TypeScript APIs, and CLIs. It activates on documentation requests and PRs that change tool registration, CLI dispatch, or exported types.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 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/agents/mcp-tool-docs-wasp-drone.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/mcp-tool-docs-wasp-drone

## What it does

The subagent reads project source and turns its behavior into reference docs for tools, APIs, and command-line interfaces. For each MCP tool, it records the purpose, input schema, possible outputs, and side effects. It can generate TypeScript API references with TypeDoc, or use API Extractor for a public contract that can be reviewed across changes. CLI docs cover commands, flags, defaults, and side effects.

It also compares docs with current code and ties changelog entries to the released artifact's version. Hivemind serves as the worked example. The subagent documents what the code does; it does not judge protocol correctness. Its scope excludes MCP protocol internals, OpenAPI/REST documentation, standalone README writing, and docs-site hosting.

## 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
```

2. **Manually: put the files in place**
- File: `.claude/agents/mcp-tool-docs-wasp-drone.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/mcp-tool-docs-wasp-drone.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/mcp-tool-docs-wasp-drone.md` — Cursor also reads .claude/agents/

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/agents/mcp-tool-docs-wasp-drone.md

## When to use it
- document an MCP tool from its schema and implementation
- generate a reference for exported TypeScript APIs
- record CLI commands, flags, and defaults
- find documentation that has drifted from the code
- tie a changelog entry to a release version

## Example prompts
- Document the MCP tools from their source and schemas.
- Compare the CLI reference with its command dispatch and flags.
- Generate the public TypeScript API reference and review the changelog.

## Similar
- [jsdoc-typescript-docs](https://affpapa.org/en/nevibecode/skills/jsdoc-typescript-docs.md) — skill · 572 installs
- [typescript-docs](https://affpapa.org/en/nevibecode/skills/typescript-docs.md) — skill · 4500 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
- [StitchAPI Docs](https://affpapa.org/en/nevibecode/mcp/rejifald-stitchapi-docs.md) — MCP server · 722 installs
- [project-docs](https://affpapa.org/en/nevibecode/skills/agent-skills-project-docs.md) — skill · 721 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
