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]>
6.0 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Google Drive Connector | Let agents search and read Drive files, and optionally create or copy them. Deleting and sharing are not exposed. Groups, scope, and a read test. |
Google Drive
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 search Drive, read file metadata and content, and on a creating connection add new files or copy existing ones.
Deleting, moving, renaming, and changing who a file is shared with are not exposed by this connector, in either capability group.
Warning: Google Drive needs Google Workspace Developer Preview registration before tools can run. 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 files you want agents to use.
- Developer Preview registration for that account, confirmed by Google.
- If your instance is not enrolled with Paperclip Cloud, you will need your own Google OAuth client with the Drive API and Drive 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 | Search files, read metadata and content, list recent files, read a file's permissions | drive.readonly |
| Read & create | The above, plus create a new file and copy an existing one | drive.readonly, drive.file |
The group is fixed for the life of the connection; to change it, make a new connection.
Connect Google Drive
- Open Connectors and select Google Drive.
- 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
File reach comes from Google. The connection sees what the authorizing account can already open: files it owns, files shared with it, and shared-drive content it is a member of. Paperclip has no file or folder picker, so narrowing access means changing sharing in Drive or authorizing with a more limited account.
Reviewed operations:
| Operation | Group |
|---|---|
search-files, list-recent-files |
Both |
get-file-metadata, read-file-content, download-file-content |
Both |
get-file-permissions |
Both |
create-file, copy-file |
Read & create only |
Two distinctions worth keeping straight. Metadata and content are separate operations, so an agent can list a file it cannot usefully parse. And get-file-permissions reads the sharing list — it does not change it.
Note: The write group's
drive.filescope only covers files the app itself created or opened, which is why creating and copying are available but editing arbitrary existing files is not. The connector's guidance is that file creation and copying should be approved; leave them on Ask first.
How connector access works covers identity and agent selection.
Try it
Search my Google Drive for a document containing "quarterly plan" and tell me its title, owner, and last modified date. Do not open or change anything else.
Expect metadata for a file you can find yourself in Drive. This confirms the credential, the account, and the agent's permission without writing anything.
Note: Illustrative task, not a recorded test result.
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 Drive profile | Use your own Google OAuth app |
| Search finds nothing you expected | The file is not shared with the authorizing account, or is on a shared drive it does not belong to | Share the file or add the account to the shared drive |
| A file is listed but its content will not read | The file type has no extractable text, or it is a link to an external item | Check the file type; metadata and content are separate capabilities |
| Create or copy is missing | The connection was made with Read only | Make a connection with Read & create |
| An agent cannot delete or re-share a file | Expected — those are not exposed | Do it in Drive |
| Needs attention | The Google token expired or was revoked | Select Reconnect |
Limitations: one connection covers one Google account. No delete, move, rename, or sharing changes. Editing an existing arbitrary file is not available; for document editing use Google Docs, Google Sheets, or Google Slides. Developer Preview applies.
Related guides
- Google Docs, Google Sheets, Google Slides — edit content inside specific file types.
- Google Workspace Search — one read-only search across Gmail, Drive, Calendar, and Chat.
- How connector access works
- Google Drive API MCP reference