Strunk

io.strunkPublished by strunk.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Publish drafts to Google Docs for review, then revise and resolve reviewer comments in your AI tool

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant publish drafts to Google Docs for review and then revise and resolve reviewer comments from within the AI tool.

What you can do
This remote server connects an AI assistant to Google Docs review workflows. According to its description, it lets you publish drafts to Google Docs for review, then revise the document and resolve reviewer comments without leaving your AI tool. No individual tools are listed in the available information.
When to use it
Useful when drafts need human review in Google Docs and you want the assistant to act on the resulting comments in the same session. Less relevant if you do not use Google Docs for review.
Requirements
A remote MCP endpoint at strunk.io over streamable HTTP. OAuth authentication is required, so you need a Strunk account and a Google account that can access the relevant documents. No environment variables or headers are declared.
Before you install
The server requires OAuth access to your Google Docs, so it can likely read and modify documents you grant it. Publishing drafts and resolving comments change shared documents that reviewers may see; confirm scope and permissions before use.

Installation

In SourceWeft

  1. Open Strunk in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.strunk%2Fgoogle-docs-comments/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "strunk": {
      "type": "http",
      "url": "https://strunk.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.