39633c2217
Connector catalog, setup guides, and shared access documentation, followed by a final code-accuracy repair pass. This PR does not change application behavior. ## Final accuracy pass Checked against shipped Paperclip `v2026.916.0`, commit `dffc2b3ca1b9e88fa21cb17493083e682dffd1ca`, rather than the dirty local checkout or the earlier canary baseline. - Corrects connector/method-specific identity choices, human audiences, and managed GitHub versus PAT scope and verification. - Explains that **Always allow** covers different arguments for the same agent/action/connection, with project scope when present; uses actual button labels and removes the test-panel control from review instructions. - Qualifies new-action quarantine, including safe-default read exceptions. Removes unconditional approval guarantees. - Separates provider channel/repository reach from Paperclip sender authorization. - Completes sandbox sign-in and model credential-selection instructions from the current UI implementation. - Repairs Notion's hub summary, removes incomplete optional Notion/Sentry client-registration procedures, and corrects Linear's provider-versus-Paperclip attribution. - Removes unsupported Postman tier claims, contradictory Cloudinary/Mem0 verification assertions, API-equivalence claims, and overbroad successful-test assurances. - Retains Supabase's required project reference: both released method definitions explicitly require it. An earlier review suggested otherwise; release code is authoritative here. - Updates the release baseline and removes draft commit chronology from the public introduction. ## Availability and remaining runtime gates - **Google:** Verification is pending. Per the product-owner clarification, authorization can continue where Google offers an Advanced option; this is not available for every account and does not override Workspace policy or other Google prerequisites. Notices on the hub and all Google guides now distinguish an unverified-app warning from blocked authorization. - **Slack is available but not yet fully functional; follow-up fixes are planned.** For agent tools, the released OAuth endpoint/scope defaults differ from Slack's documented MCP contract. The page now warns against treating that route as production-ready and removes the misleading bot-scope walkthrough. Chat-channel bot setup remains separate. Engineering must reconcile the integration and run OAuth plus one read before removing this warning. Source: https://docs.slack.dev/ai/slack-mcp-server/ - No credentialed connector run was performed in this pass. Code consistency, provider documentation, UI rendering, and successful live execution are separate evidence levels. No claim of runtime certification for all connectors. ## Validation - Root build: 253 crawlable documentation pages. - Full `docs:test`: all eight suites passed locally, including root/subpath routes, sitemap history, fingerprints, navigation, skill source blocks, crawlable links, doc-link resolution, and SEO metadata. - Internal-link lint: 258 Markdown files; no broken internal links. - Latest cleanup: full build, all eight docs:test suites, internal-link lint and diff whitespace checks passed; 1,878 link-resolution checks. - Fixed the Calendar MCP reference URL; browser-checked the five inconclusive external destinations (Miro article loads; Asana, Google Cloud, OpenAI and xAI reach sign-in/console screens). Authenticated destinations were not tested beyond those screens. - Replaced the Sandbox providers editorial TODO with a scope note and removed the CLI overview's unfinished-guide announcement. - Browser client navigation: 687 checks passed using installed Chrome. Initial launch lacked the downloaded Playwright browser; rerun used `DOCS_CHROMIUM_PATH` without changing the tests. - Nine representative connector/shared pages at 1440px and 390px: HTTP 200, one article H1, no page-level horizontal overflow. Mobile screenshot inspected; approval page opened in the Codex browser. - Navigation audit reports three existing non-connector orphan files; this patch does not alter those files or their navigation. The previous revision's provider-page expansion, Google shared setup guide, navigation additions, and accidental node_modules-symlink cleanup remain in this PR. Internal review ledgers remain outside the publication branch. No merge or production deployment authorized. --------- Co-authored-by: DevRel Gemini <[email protected]> Co-authored-by: Paperclip <[email protected]> Co-authored-by: Claude Opus 5 (1M context) <[email protected]> Co-authored-by: Michael Nguyen <[email protected]>
5.7 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Google Docs Connector | Let agents read Google Docs documents and optionally update them. Capability groups, document scope, what editing covers, a read test, and troubleshooting. |
Google Docs
Warning: Google verification pending. Paperclip has not yet completed Google app verification. You may see an unverified-app warning during authorization. If Google offers an Advanced option to continue to Paperclip, you can choose to proceed after reviewing the requested access. This option is not available for every account; Workspace administrator restrictions and other Google access requirements still apply. Contact [email protected] if you cannot connect.
Agents can read the text and structure of Google Docs documents, and on an editing connection update them.
Warning: Google Docs needs Google Workspace Developer Preview registration before it will authorize. Google must register the Workspace email that signs in, and the Cloud project that owns the OAuth client if you bring your own. Apply first at Google Workspace Developer Preview.
Before you connect
- A Google Workspace account that can already open the documents you want agents to use.
- Developer Preview registration for that account, confirmed by Google.
- Without Paperclip Cloud enrollment, you need your own Google OAuth client with the Drive API, Docs API, and Docs MCP API enabled. Set up your own Google OAuth app is the complete procedure — do it before you start here.
Pick a capability group
| Group | What agents can do | Scopes requested |
|---|---|---|
| Read only | Read document text and structure | drive.readonly, documents.readonly |
| Read & edit | The above, plus update a document | drive.readonly, drive.file, documents |
The group is fixed for the life of the connection.
Connect Google Docs
- Open Connectors and select Google Docs.
- On the Access step, choose the identity and which agents may use the connection.
- Choose the capability group, then Connect with Paperclip or Use your own Google OAuth app — the latter needs the client ID and secret from Set up your own Google OAuth app.
- Complete Google's consent screen with the registered Workspace account.
Choose access
Document reach comes from Google: the connection can open what the authorizing account can open. There is no document picker in Paperclip.
Reviewed operations:
| Operation | Group |
|---|---|
read-doc |
Both |
update-doc |
Read & edit only |
This is a deliberately small surface: two operations, not a Docs editor. update-doc applies changes through the Docs API, so what it can express is whatever that API accepts — check the operation's schema on the Permissions tab before planning work that depends on a particular kind of edit. What is definitely absent is anything beyond these two operations: there is no separate tool here for comments, suggestions, or revision history.
Note: The connector's guidance is that document updates should be approved. Leave
update-docon Ask first; an edit lands in a real document that other people may be working in.
How connector access works covers identity and agent selection.
Try it
Identify the document by its URL, not its title, and pick something in it you already know. Substitute both:
Read this Google Doc — https://docs.google.com/document/d/YOUR_DOC_ID/edit — and
tell me the text of its first heading. Do not edit it.
Expect the heading you can see for yourself.
Warning: Do not test with "the document titled X". The reviewed operation here is
read-doc, which takes a document identifier — there is no document-search tool on this connector. A title-based request makes the agent guess or fail for reasons that have nothing to do with your setup. If you genuinely need title search, that is Google Drive or Google Workspace Search.
If you want to confirm editing, do it on a scratch document you created for the purpose, not a live one.
Note: Illustrative task, not a recorded test result. Substitute a document URL or ID you can open and a value you already know.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Google refuses before the consent screen | Developer Preview registration is incomplete | Finish registration and retry |
| Connect with Paperclip is not offered | The instance is not enrolled with Paperclip Cloud, or Cloud is not advertising the Docs profile | Use your own Google OAuth app |
| A document cannot be found | It is not shared with the authorizing account | Share it in Google Drive; no reconnect needed |
update-doc is missing |
The connection was made with Read only | Make a connection with Read & edit |
| An edit did not produce the formatting you expected | The update goes through the Docs API, which does not cover every editor feature | Finish the formatting in Google Docs |
| Needs attention | The Google token expired or was revoked | Select Reconnect |
Limitations: one connection covers one Google account. Creating a document is not part of this connector — use Google Drive with the create group. Comments, suggestions, and revision history are not exposed. Developer Preview applies.
Related guides
- Google Drive — find and create files.
- How connector access works
- Verify a connector and fix a broken one
- Google Docs API MCP reference