-
Notifications
You must be signed in to change notification settings - Fork 153
Comparing changes
Open a pull request
base repository: a-bonus/google-docs-mcp
base: v1.3.0
head repository: a-bonus/google-docs-mcp
compare: v1.4.0
- 13 commits
- 14 files changed
- 8 contributors
Commits on Mar 20, 2026
-
style: apply prettier formatting to Sheets grouping tools
Keep formatting in groupRows and ungroupAllRows aligned with Prettier output so format checks pass consistently in CI. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for cd5e8be - Browse repository at this point
Copy the full SHA cd5e8beView commit details -
Cut a patch release to republish after fixing CI formatting issues that affected the 1.3.0 release flow. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 13f1c7d - Browse repository at this point
Copy the full SHA 13f1c7dView commit details
Commits on Mar 21, 2026
-
feat: add addTab tool for creating new tabs in Google Docs
Adds a new `addTab` tool that creates tabs in Google Docs documents using the batchUpdate API's `addDocumentTab` request. Supports optional title, parentTabId (for nesting), index (positioning), and iconEmoji. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for af4ad8a - Browse repository at this point
Copy the full SHA af4ad8aView commit details -
Configuration menu - View commit details
-
Copy full SHA for e5c4504 - Browse repository at this point
Copy the full SHA e5c4504View commit details
Commits on Mar 22, 2026
-
fix: use localhost instead of 127.0.0.1 for OAuth redirect URI
Google's OAuth for Desktop App clients only accepts http://localhost redirects, not http://127.0.0.1. Using the IP literal causes a 400 Bad Request error during the authorization flow. Fixes #90
Configuration menu - View commit details
-
Copy full SHA for 8853b62 - Browse repository at this point
Copy the full SHA 8853b62View commit details
Commits on Mar 23, 2026
-
Fall back to Drive export when Docs API returns 403
Some Google Workspace admins restrict third-party access to the Docs API while allowing the Drive API. In that case, docs.documents.get() returns 403 even for documents the user owns in a Shared Drive. When readDocument receives a 403 and the requested format is 'text', fall back to drive.files.export() with mimeType 'text/plain'. The Drive API is more permissive in enterprise environments and already handles Shared Drive access correctly elsewhere in the codebase. Fixes #92, relates to #33
Configuration menu - View commit details
-
Copy full SHA for 6a109a8 - Browse repository at this point
Copy the full SHA 6a109a8View commit details -
feat: add modifyText and findAndReplace tools
modifyText combines text replacement/insertion and formatting in one atomic batchUpdate call. Supports insert, replace, format-only, and combined modes with text-search or index-based targeting. findAndReplace wraps the native replaceAllText API request with tab-scoping support via tabsCriteria. Both tools include comprehensive Vitest test suites. Made-with: Cursor
Configuration menu - View commit details
-
Copy full SHA for 030e475 - Browse repository at this point
Copy the full SHA 030e475View commit details -
Merge pull request #91 from Asborien/fix/oauth-localhost-redirect
fix: use localhost instead of 127.0.0.1 for OAuth redirect URI
Configuration menu - View commit details
-
Copy full SHA for 3168d95 - Browse repository at this point
Copy the full SHA 3168d95View commit details -
Merge pull request #93 from andrie/fix/shared-drive-403-fallback
Fall back to Drive export when Docs API returns 403 (Shared Drive / Workspace policy fix)
Configuration menu - View commit details
-
Copy full SHA for bd5b21d - Browse repository at this point
Copy the full SHA bd5b21dView commit details -
Merge pull request #94 from Mawox/feat/modify-text-find-replace
feat: add modifyText and findAndReplace tools
Configuration menu - View commit details
-
Copy full SHA for b4fac35 - Browse repository at this point
Copy the full SHA b4fac35View commit details -
feat: add replaceRangeWithMarkdown tool for surgical markdown edits
Adds a new tool that replaces a specific character range in a Google Doc with formatted markdown content. This enables targeted edits (e.g. fixing a single section) without replacing the entire document. The tool deletes the specified range then inserts markdown at that position using the existing insertMarkdown pipeline, supporting all formatting including headings, lists, tables, code blocks, and inline styles.
Configuration menu - View commit details
-
Copy full SHA for a111094 - Browse repository at this point
Copy the full SHA a111094View commit details -
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 564d249 - Browse repository at this point
Copy the full SHA 564d249View commit details -
Merge pull request #95 from haseeb-asad/feat/replace-range-with-markdown
feat: add replaceRangeWithMarkdown tool for surgical markdown edits
Configuration menu - View commit details
-
Copy full SHA for 304ce9f - Browse repository at this point
Copy the full SHA 304ce9fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.3.0...v1.4.0