Write in Claude
Draft specs, memos, and plans where your repo, tools, and source material are already available.
Claude writes the doc. Google Docs hosts the review.
Strunk publishes Claude-written docs to Google Docs, pulls reviewer comments back into Claude, and applies approved revisions without breaking comment threads.
Draft specs, memos, and plans where your repo, tools, and source material are already available.
Share a native Google Doc so reviewers can comment without installing anything new.
Bring comments back to Claude, approve the edits, and update the same doc.
The round trip
Strunk creates a Google Doc from the draft you already wrote in Claude.
They use Google Docs comments, so you do not have to collect feedback by hand.
Comments come back to the same place that has your source files and working context.
Strunk replies, updates the doc, and keeps existing comment threads intact.
Pricing
Included in both plans
$19/mo
Pay monthly after your free 7-day trial.
Start free trial$8.25/mo
$99 billed annually after your free 7-day trial.
Start free trialFAQ
No. Reviewers comment in the Google Doc you share with them, just like they normally would.
No. Strunk is the bridge between Claude and Google Docs. You still write in Claude and review in Docs.
Yes. Strunk works as a remote MCP connector in Claude chat and Cowork through Claude Connectors, and in Claude Code through Claude.ai connectors or the claude mcp CLI.
Strunk uses Google's limited drive.file permission. It can work with docs it creates or docs you explicitly open with it, not your whole Drive.
No. Strunk does not store doc bodies, titles, URLs, or comment text. It only stores the minimal mapping needed to update the right Google Doc.
No. Strunk updates the existing doc instead of replacing it, so reviewer threads stay attached.
You do. Claude can draft a response and revision, but Strunk only applies changes after you approve them in the harness.
Ready when your next doc is