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]>
3.9 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Recognized but Unlisted Providers | The provider definitions present in the Paperclip catalog but withheld from the Connectors list, and the providers that gate access behind their own approval. |
Providers Paperclip recognizes but does not list
Reference for the inventory behind the catalog. If you are looking for a connector to set up, start at Connectors — everything on this page is either withheld from the Connectors list or blocked by the provider, so none of it can be set up from the catalog today.
Two separate things get confused here, so they are listed separately. A withheld provider has a complete definition that Paperclip still recognizes, but it is deliberately kept out of the customer-facing list. A provider-gated one is not offered because the provider itself will not let an independently registered client connect.
Note: Checked against Paperclip v2026.916.0. Catalog visibility can change between releases; recognition is not a promise of availability. Existing connections still need to be verified independently.
Withheld from the Connectors list
Paperclip keeps recognition and visibility as separate things: a definition can stay in the catalog while being hidden from the store. The comment on the hidden set in the App source gives the reason — separating the two means pulling a provider out of the list does not have to break connections somebody already saved.
What we can confirm at this commit: the definitions below are present, Paperclip still resolves them, and they are filtered out of the list you browse. What we did not do is connect or run any of them, so whether a connection saved earlier still works is unverified here. If you have one, Verify a connector and fix a broken one is how to find out, and the answer is specific to your instance.
None of these have connector pages, and none can be added from the catalog.
| Provider | Slug |
|---|---|
| beehiiv | beehiiv |
| Bitly | bitly |
| Brex | brex |
| Candid | candid |
| Coda | coda |
| Composio | composio |
| Context7 | context7 |
| Egnyte | egnyte |
| Embat | embat |
| Kernel | kernel |
| Local Falcon | local-falcon |
| Make | make |
| Manufact | manufact |
| O'Reilly | oreilly |
| PlanetScale | planetscale |
| Razorpay | razorpay |
| Sanity | sanity |
| Similarweb | similarweb |
| Ticket Tailor | ticket-tailor |
| TickTick | ticktick |
| Xero | xero |
Gated by the provider
These three are recorded as blocked because of a requirement on the provider's side. The requirement is theirs, not Paperclip's, and it has to be lifted or granted by them — there is no setting in Paperclip that works around it.
| Provider | What the provider requires |
|---|---|
G2 (g2) |
G2 has to enable cross-application token introspection before an independently registered client can connect at all. There is no customer-side application process for this. |
Vercel (vercel) |
Vercel reviews and approves MCP clients. Approval is between Vercel and the client's publisher, so an operator cannot request it for their own instance. |
Zomato (zomato) |
Zomato limits third-party clients and requires each redirect URI to be allowlisted. Both steps happen on Zomato's side. |
If you need one of these now, the routes that do not depend on the provider's client approval are in Can't find your app? — a custom server where the provider permits one, automation you already own, or a workspace and a CLI.
Related
- Connectors — the catalog you can actually set up from.
- Connect a custom MCP server — the path for a service with no catalog entry.
- Verify a connector and fix a broken one — checking whether a connection you already have still works.