Help

Last updated: September 6, 2026

Strunk is a bridge between your AI tool (Claude Code, Codex, and other MCP clients) and the doc tools your reviewers already use. You draft and revise where your repo, tools, and data context live. Strunk publishes the doc out to Google Docs for review, pulls reviewer comments back with their anchored spans, and applies approved revisions in place, replying to and resolving threads without destroying existing comments. Google Docs stays the source of truth.

Getting help

Email support@strunk.io, or use the chat widget in the corner of the page.

Before you start

A Strunk account. Sign up with your Google account, free.
A Google account, connected once so Strunk can create and update Google Docs on your behalf.
An AI tool that supports MCP. Any client that installs a remote MCP server over streamable HTTP works.

Connect Strunk

Strunk is a remote MCP server. Add it to your AI tool as a connector using the server URL below. Authentication runs over OAuth 2.0, so there are no API keys to paste.

https://strunk.io/mcp

Add the server URL above as a custom connector in Claude (Settings → Connectors → Add custom connector), or via your tool's MCP config.
Sign in when the OAuth window opens and approve access.
The first time you publish or open a doc, Strunk asks you to connect Google Docs. Strunk uses Google's limited drive.file permission, so it only touches docs it creates or files you explicitly open with Strunk.

The round-trip

A typical review cycle, all driven from your AI tool:

Publish. Strunk renders your markdown draft into a new Google Doc and returns its URL. Re-publishing the same doc applies a targeted diff, so existing reviewer comments and their anchors survive.
Share. Send the Google Doc to your reviewers. They comment in Google Docs, the tool they already know.
Pull. Strunk brings comments back into your AI tool with the exact quoted spans, resolved status, and threaded replies, so you can triage with full context.
Revise. You approve revisions in your AI tool, and Strunk applies them as direct edits on the commented spans.
Reply and resolve. Strunk replies to each thread in your voice, and resolves it once you have decided how to handle the comment.

Tools

Strunk exposes a small set of purpose-built tools. Each one tells your AI tool whether it only reads or can change a doc, which is what most clients use to decide when to prompt you.

publish_doc publishes or re-publishes a markdown draft to Google Docs.
pick_google_doc connects an existing Google Doc so Strunk can pull its comments and revise it.
pull_comments reads reviewer comments back with their anchored spans (read-only).
inspect_doc reads the current doc structure, so you can verify an edit landed (read-only).
apply_revisions applies author-approved edits onto the commented spans.
reply_comment replies to a comment thread.
resolve_comment resolves a handled thread.
get_preferences and set_preferences read and update your reply, resolve, and sharing preferences.
get_writing_rules returns your writing rules, so your AI tool can draft in your voice (read-only).
get_review_workflow returns how your AI tool triages and answers reviewer comments (read-only).

How Strunk triages comments

Strunk does not choose revisions for you. The workflow it hands your AI tool puts each substantive change to you before it goes out, and it marks the tools that change a doc so your client prompts you first. Comments fall into three tiers: mechanical (typos, dead links, formatting, drafted and applied on your ok), judgment calls (a tradeoff you decide before Strunk writes anything in your voice), and needs context (surfaced, never fabricated). For each comment the order is reply first, then apply the edit, then resolve, so the acknowledgment stays tied to the reviewer's span even if the edit removes it.

Your data

Strunk does not store Google Doc bodies, titles, URLs, or reviewer comment text. Those stay in Google Docs. It keeps only the minimal mapping needed to update the right doc. Google refresh tokens are custodied by WorkOS rather than stored in Strunk's database. You can revoke Strunk's access at any time from your Google account settings. See the Privacy Policy for details on what Strunk processes and how.