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.0 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Webflow Connector | Let agents work with Webflow sites and CMS collections. How roles limit reach, CMS content versus publishing, a read test, and troubleshooting. |
Webflow
Agents can work with your Webflow sites — reading site structure and working with CMS collections and their items.
The practical case is CMS content: an agent drafting, checking, or updating collection items. Webflow also exposes Designer tools for canvas, styles and layout at the same endpoint, but they carry a prerequisite that rarely suits agent work — see Designer tools.
Before you connect
- A Webflow account with access to the sites you want agents to use.
- Your workspace and site roles decide what the connection can reach. A limited role means a limited connection, which is often what you want.
Connect Webflow
- Open Connectors and select Webflow.
- On the Access step, choose the identity and which agents may use the connection.
- Select Sign in with Webflow and complete browser sign-in, authorizing the sites you want when Webflow asks.
Paperclip registers its client automatically, so there is nothing to configure in a developer console.
Choose access
Site reach is Webflow's decision: the sites the authorizing account can access under its workspace and site roles, plus whatever you authorized. Paperclip has no site picker.
The distinction that matters most is between changing content and making it live:
| Operation | Effect |
|---|---|
| Reading sites, collections, and items | Nothing changes |
| Creating or updating CMS items | Changes content in Webflow |
| Publishing | Makes changes visible on the live site |
Warning: Publishing is the consequential one. A publish can push every pending change on a site live, not only the item an agent was working on — including edits colleagues had staged and not yet finished. Keep publish actions Off and let a person publish from Webflow.
See Set action permissions for setting each of these.
Designer tools
Webflow's MCP server does expose Designer tools — canvas, styles and layout — and they are served from the same endpoint this connector uses. They are not unavailable; they are conditional.
The condition is a companion app. Webflow states that "the MCP Companion App must remain open in the Webflow Designer for Designer API tools to function," launched from the Apps panel with the Designer open. Close it and the canvas operations stop working.
That prerequisite is a poor fit for unattended agent work, because it requires a person to have the Designer open for the duration. Plan Designer work as something a person drives, and use this connector for CMS content.
Note: We have not run Webflow Designer tools through Paperclip. What is established here is the provider's own requirement, not a tested Paperclip result — so if you do try it, treat it as unverified and start on a site that does not matter. Webflow's MCP getting started is the authority on the current tool surface.
Try it
List the CMS collections on the marketing site and tell me how many items are in the blog collection. Do not create, change, or publish anything.
Compare against the Webflow dashboard. Reading collection structure confirms the credential and the site scope without touching content or the live site.
Note: Illustrative task, not a recorded test result. Substitute a site and collection from your own account.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| A site is missing | The account's workspace or site role does not include it, or it was not authorized | Adjust the role in Webflow, or reconnect and authorize it |
| A CMS field is missing | Certain field types are not exposed, or the field is on a different collection | Check the collection schema in Webflow |
| A change is not visible on the live site | CMS changes require publishing | Publish from Webflow when the change is ready |
| A site published unexpectedly | A publish action was set to Allowed | Set it to Off; review what went live in Webflow |
| A Designer tool fails or is unavailable | The MCP Companion App is not open in the Webflow Designer; it must stay open for Designer tools to work | Open it from the Apps panel, or do the design work in the Designer directly |
| Needs attention | The grant was revoked | Select Reconnect |
Limitations: one Webflow account per connection. No site filter inside Paperclip. Designer tools need a companion app kept open in the Designer, so they do not suit unattended work. Webflow's plan limits apply to CMS item counts and API rates.
Related guides
- Wix — another website platform connector.
- Set action permissions
- How connector access works
- Webflow MCP getting started