Strunk MCP server
Commit Nov 12, 2026Publish drafts to Google Docs and manage reviewer comments directly within your AI agent.
Also known as firstcrack-studio/strunk-plugin, google-docs-comments
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.2
- Last commit
- Nov 12, 2026
- License
- MIT
What is Strunk MCP?
Strunk publishes drafts to Google Docs and manage reviewer comments directly within your AI agent.
Summary generated from the project's README
About Strunk MCP server
Managing Google Docs drafts and reviewer feedback from within an AI agent is what Strunk enables for writers and editors. By connecting to a remote MCP server via Streamable HTTP, users can use tools like publish_doc, pull_comments, and apply_revisions to handle the entire writing lifecycle. The server requires WorkOS/AuthKit OAuth for authentication and connects to Google Docs using the drive.file scope to manage specific files.
Developers using Claude Code, Hermes Agent, or VS Code can access atomic transport tools and specialized slash commands like /strunk:publish. The system is designed to keep writing rules and review workflows live from the backend, ensuring that instructions remain current without needing plugin updates. While the server handles the logic, the client manages the connection, with Hermes specifically handling the storage and refreshing of OAuth tokens.
What you can do with it
- 1Publishing written draftsSend your current writing draft directly to a new or existing Google Doc.
- 2Managing reviewer feedbackRetrieve and respond to comments left by reviewers on your documents.
- 3Applying document revisionsUse the agent to make direct edits to your Google Docs based on feedback.
- 4Resolving comment threadsClean up your document by marking comment threads as resolved through the AI interface.
Written from the project's README. Every use case is checked against a quote from it.
How to install Strunk MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Strunk MCP in Claude Code
$ claude mcp add --transport http google-docs-comments https://strunk.io/mcpInstall Strunk MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"google-docs-comments": {
"url": "https://strunk.io/mcp"
}
}
}Install Strunk MCP in VS Code
.vscode/mcp.json
{
"servers": {
"google-docs-comments": {
"type": "http",
"url": "https://strunk.io/mcp"
}
}
}Install Strunk MCP in VS Code CLI
$ code --add-mcp '{"name":"google-docs-comments","type":"http","url":"https://strunk.io/mcp"}'Install Strunk MCP in Codex
$ codex mcp add google-docs-comments --url https://strunk.io/mcpInstall Strunk MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.google-docs-comments] url = "https://strunk.io/mcp"
Install Strunk MCP in Gemini CLI
$ gemini mcp add -s user --transport http google-docs-comments https://strunk.io/mcpInstall Strunk MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"google-docs-comments": {
"url": "https://strunk.io/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablefirstcrack-studio/strunk-plugin is public and reachablegithub.com/firstcrack-studio/strunk-plugin ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/firstcrack-studio/strunk-plugin ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubStrunk plugin
The install-once bundle of Strunk. Claude Code reads .claude-plugin/plugin.json and .mcp.json.
Hermes Agent, VS Code and other Agent Plugins hosts read plugin.json and mcp.json. Both point at
the same server and the same skills.
- The Strunk remote MCP (
.mcp.json,mcp.json), served over Streamable HTTP athttps://strunk.io/mcpand protected by WorkOS/AuthKit OAuth. It carries the atomic transport tools:publish_doc,pick_google_doc,pull_comments,apply_revisions,reply_comment,resolve_comment,inspect_doc,get_preferences,set_preferences,get_account,get_version,get_review_workflowandget_writing_rules. - Slash commands (
commands/, Claude Code only):/strunk:pull-comments,/strunk:publish,/strunk:link-doc. - Two skills.
skills/strunk-review/makes a session reach for Strunk when the author mentions a doc that came back with comments.skills/strunk-setup/walks the two connections Strunk needs. SETUP.md, followed on install, which ends at the author's first review rather than at "connected".
Every one of these is a launcher. The review workflow, the triage tiers and the author's writing
rules are not bundled here. get_review_workflow and get_writing_rules serve them live from the
Strunk backend, so they stay current without a plugin update and work on any harness that connects to
the MCP. The non-negotiable invariants ride in the MCP instructions field, present the moment the
server connects and before any tool call.
That split is deliberate: a bundled copy of the judgment drifts from the server that owns it, which is why the original bundled skill was removed. Commands and skills here point at the server. They never restate it.
Hermes Agent
Needs Hermes 0.23.1 or later.
hermes plugins install strunk
hermes mcp add strunk --url https://strunk.io/mcp --auth oauth
The second command signs you in to Strunk. Your browser opens; if it does not, run
hermes mcp login strunk. Then start a new session, or run /reload-mcp, so the tools load. The
first time you publish or open a doc, Strunk asks you to connect Google Docs.
What to know before installing:
- Network. Every tool call goes to
https://strunk.io/mcp. Publishing sends the draft you publish. Pulling comments returns reviewers' comments, names and the spans they anchor to. That content also reaches your model provider through the session, like anything else the agent reads. - Google access. Strunk uses Google's
drive.filescope, which covers only the docs Strunk creates and the files you pick for it. - Write tools change your Google Docs. Publishing creates or updates a doc. Revising edits it. Replying and resolving act on comment threads under your Google account.
- Approvals. The package marks the
strunkserver untrusted, so Hermes asks before each write call. The sign-in command above writes its ownstrunkentry to~/.hermes/config.yaml, which replaces the package's, trust included. To keep the approval prompt, addtrust: untrustedundermcp_servers.strunkin that file. - Credentials. Hermes stores and refreshes the Strunk OAuth token. Your Google refresh token is held by WorkOS, Strunk's sign-in provider, and never reaches your machine. Nothing in this package reads either one.
- No local code. The package is two manifests and Markdown. The tool list comes from Strunk's server at run time, so the pinned commit does not cover it.
Privacy policy: https://strunk.io/privacy
Install and usage on other tools: see the repo README.
Strunk MCP questions
How do I add Strunk MCP to Claude Code?
Run claude mcp add --transport http google-docs-comments https://strunk.io/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Strunk MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How does Strunk access my Google Docs?
Strunk uses Google's drive.file scope, which limits access to only the documents that Strunk creates or that you specifically select for it.
Will using this tool change my existing documents?
Yes, write tools can modify your Google Docs by creating or updating documents, editing them, or acting on comment threads.
Where are my Google credentials stored?
Your Google refresh token is held by WorkOS, the sign-in provider, and is never stored on your local machine.