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]>
4.9 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Cloudflare Connector | Let agents work with Cloudflare accounts, zones, and resources. What one connection reaches, configuration risk, a read test, and fixes. |
Cloudflare
Agents can work with your Cloudflare account through Cloudflare's hosted server — inspecting zones, DNS, and the resources your account manages.
Warning: Do not assume one connection reaches every Cloudflare product. Cloudflare publishes a range of capabilities and changes them; what your agent gets is what the hosted server exposes to your credential. Read the connection's action list rather than planning work from Cloudflare's product catalogue.
Before you connect
- A Cloudflare account with access to the zones and resources you want agents to use.
- If using a key rather than browser sign-in, a Cloudflare API token created with only the permissions you intend to grant.
Cloudflare's API tokens are precise — you can scope them to specific zones, accounts, and permission groups. That is the strongest control available on this connector, and it is worth using rather than reaching for an account-wide token.
Connect Cloudflare
- Open Connectors and select Cloudflare.
- On the Access step, choose the identity and which agents may use the connection.
- Choose how to authenticate:
- Sign in with Cloudflare — browser sign-in, which carries the signed-in user's access.
- Use an API key — paste a Cloudflare API token, which carries exactly the scope you gave it.
- Finish setup.
Prefer the API token path when you want a narrow, auditable boundary. Prefer browser sign-in when you want the quickest setup and the account is already limited.
Choose access
Reach is Cloudflare's decision: the account, zones, and resources the credential permits. There is no zone picker in Paperclip.
Three categories of action worth separating, because they carry very different consequences:
| Category | Kind of action | Suggested setting |
|---|---|---|
| Reads | Listing and reading configuration or analytics | Allowed |
| Configuration writes | Changing how traffic is routed, filtered, or cached | Ask first |
| Provisioning and deletion | Creating or removing resources | Off unless specifically needed |
Note: Cloudflare's hosted endpoint covers a wide product surface and its tool list is the provider's to change. Sort the live list on the Permissions tab into these three categories for the connection you actually made, rather than assuming a particular DNS or firewall tool is present — availability also depends on the permission groups on your token.
Warning: Configuration changes here take effect on live traffic. A DNS or firewall edit can take a site off the internet within seconds, and provisioning new resources can incur charges on the account. Keep writes behind approval.
Try it
List the Cloudflare zones this account can see and tell me the DNS record count for one of them. Do not change any record.
Compare the zone list against the Cloudflare dashboard, and check it contains exactly the zones you meant the token to cover — no more. A zone listing confirms the credential and shows you the scope at the same time, which is the quickest way to catch a token that was scoped more broadly than you intended.
Then confirm the calls appear in the connection's activity, so you know the list came from Cloudflare rather than from the agent's recollection.
Do not verify with a DNS or firewall change on a live zone.
Note: Illustrative task, not a recorded test result.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| The agent sees fewer zones than expected | The API token is scoped to specific zones | Widen the token deliberately, or accept the boundary |
| An action is refused | The token lacks that permission group | Add the permission in Cloudflare, or leave the capability off |
| An expected capability is absent | Cloudflare's server does not expose it to this credential | Use Refresh actions; otherwise it is unavailable |
| A configuration change broke live traffic | A write was set to Allowed | Revert in the Cloudflare dashboard, then set writes to Ask first |
| Unexpected charges appear | A provisioning action created billable resources | Review Cloudflare billing; set provisioning actions to Off |
| Needs attention | The token was revoked or the sign-in expired | Select Reconnect |
Limitations: one Cloudflare credential per connection. No zone filter inside Paperclip. Paperclip cannot undo a Cloudflare configuration change.
Related guides
- Netlify — another hosting and deployment connector.
- Set action permissions
- Answer a connector review request
- Cloudflare MCP servers