Changelog
What's new in Strunk
The features worth knowing about, newest first.
Check every draft against your writing rules
Strunk now checks your writing every time you publish, revise or reply. Choose your rules in your account, and your AI tool gets them before it writes.
- Catch the AI tells: em dashes, hedging, stock phrases.
- Turn on Strunk's rules to cut needless words and keep the voice active.
- Set your house style, from British or American spelling to the Oxford comma.
Cursor and other MCP tools
You can now connect Cursor with steps written for it. Other MCP tools have a general guide.
- Use any tool that supports remote MCP over Streamable HTTP. No plugin needed.
- Sign in with OAuth. There is no API key to paste.
Comments from every tab of a doc
Your doc can have tabs. Comments from any tab come back to you, and your fix lands in the tab it came from.
- Add or move tabs whenever you like. Strunk keeps publishing to the same one.
- Pick the tab you meant when the same text sits in two of them.
Edit tables without losing comments
Change a table in your draft and publish again. Strunk updates the table in Docs and keeps the comments on every cell you did not touch.
- Fix the exact text a reviewer commented on inside a cell.
- Keep rows that carry comments. Strunk stops and tells you which row.
- Delete that row anyway when the comment asks you to.
Strunk in Claude's Connectors Directory
You can now add Strunk from the listing in two clicks. There is no server URL to paste.
- Follow the checklist new accounts get for connecting Google and publishing a first doc.
Markdown tables publish as real tables
Tables in your draft show up as Google Docs tables. Reviewers can comment inside them.
- Read the documentation at strunk.io/docs.
Setup steps for your own tool
Pick your tool and follow steps written for it. Codex CLI, Claude Code, Claude Desktop, Claude Web and ChatGPT Desktop each have their own.
- Copy a starter prompt so you know what to say.
- See which Google account you connected on your account page.
- Reconnect from a link when your Google access runs out.
The review workflow ships with the connector
Ask your tool to work through review comments. It knows how to sort them, what order to reply and fix in, and that it needs your ok first.
Connect with one command
@strunk/cli sets everything up in one command, sign-in included.
- Ask your tool to read the published doc back, so you can check a fix landed.
Publish to a doc you already have
Strunk does not have to create the doc. Pick one you already share with reviewers and Strunk can work with it.
- Keep the rest of your Drive private. Strunk only sees the docs you pick.
Account settings in one place
One page for your settings. Choose whether Strunk replies to comments and closes threads, pick who can open new docs, and delete your account if you want.
Sign in once, with nothing to run locally
Strunk runs on our servers now. You sign in once. There is no API key and nothing to run on your machine.
- Keep your doc text private. Strunk does not store bodies, titles or comments.
Publish, pull comments, revise, resolve
Publish a draft from your AI tool to Google Docs. Pull reviewer comments back, fix the text they commented on, then reply and close the thread. Publishing again keeps their comments in place.
Want the details on how any of this works? Read the documentation, or email support@strunk.io.