Python · Google · NumPy · Sphinx · Epytext
Auto-generate Python docstrings with AI
One command writes Google, NumPy, or Sphinx docstrings for every undocumented function in your Python project — with drift detection to catch stale docs before they merge.
See it in action
Before and after — Google style
How it works
More than a docstring generator
⚡
Call graph context
Wright builds a dependency graph before generating. It reads what calls your Python function and what it calls — so docs describe purpose, not just mechanics.
📊
Coverage tracking
Know the exact percentage of documented functions across every file. Set a minimum threshold and enforce it in CI.
🔍
Drift detection
When a function signature changes, Wright flags the stale docstring automatically — as a VS Code warning and a CI failure.
🔌
MCP for AI tools
Exposes your indexed docs to Claude Code, Cursor, and Copilot via MCP so they always have live context about your codebase.
Comparison
How Wright differs from alternatives
Writing manually
Takes 5–10 min per function. Gets skipped under deadline pressure. Goes stale silently.
GitHub Copilot
Suggests one function at a time on demand. No batch generation, no coverage tracking, no drift detection.
Sphinx autodoc
Generates docs from existing docstrings — it doesn't write them. You still need to author every string.
Start documenting your Python codebase
Free VS Code extension · CLI · GitHub Action · MCP server. No credit card required.