mcp-tool-docs-wasp-drone — Claude Code subagent for documentation
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.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install documentation-tools@wasp-nestWhat mcp-tool-docs-wasp-drone 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.
What it helps with
- 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 for the agent
- 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.
How to install mcp-tool-docs-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install documentation-tools@wasp-nest2Manually: put the files in place
.claude/agents/mcp-tool-docs-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/mcp-tool-docs-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/mcp-tool-docs-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about mcp-tool-docs-wasp-drone
How do I install mcp-tool-docs-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install documentation-tools@wasp-nest. The agent file is .claude/agents/mcp-tool-docs-wasp-drone.md.
What does mcp-tool-docs-wasp-drone do?
It documents MCP tools, TypeScript public APIs, and CLIs from source code. It also checks docs against implementation and helps prepare changelog entries tied to a release.
What documentation is outside its scope?
It does not cover MCP protocol internals, OpenAPI or REST API docs and SDK generation, standalone README writing, or docs-site hosting.