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 |
|---|---|
| Shopify Connector | Give agents a store's public catalog, policies, and cart tools. This is the shopper-facing storefront surface, not Admin API access to orders or customers. |
Shopify
Agents can search a Shopify store's products and policies and work with shopping carts, the same way a shopper's assistant would.
Warning: This is Shopify's shopper-facing surface, not Admin API access. It does not reach merchant orders, customers, inventory management, or anything in Shopify Admin — not even for the merchant's own store. If you need admin data, this connector is not the route.
There is no sign-in. These are public endpoints, so what an agent can see is what any visitor to the storefront could see.
Before you connect
- The store's permanent
your-store.myshopify.comdomain. A custom domain is not the endpoint, even if that is the address customers use. - A public storefront. Shopify keeps trial storefronts private until a plan is selected, and a password-protected storefront returns an authorization error to everyone — Paperclip cannot use a merchant's Admin session to get past it.
To make a storefront public: select a Shopify plan, then in Shopify Admin open Online Store → Preferences and set storefront visibility to public, removing password protection.
Pick a server
Shopify offers two, and Paperclip exposes both:
| Option | Use it for |
|---|---|
| Shopify UCP commerce | The recommended choice. Shopify's current catalog, cart, and checkout tools |
| Storefront policies and compatibility tools | Shopify's compatibility server, when agents mainly need storefront policy and FAQ search |
Note: On the UCP option, Paperclip supplies the agent profile Shopify requires automatically. It currently sends Shopify's documented hosted profile fixture while Paperclip's own production profile is being established.
Connect Shopify
- Confirm the storefront is public.
- Open Connectors and select Shopify.
- On the Access step, choose the identity and which agents may use the connection.
- Choose the server option.
- Enter the Store domain as the bare permanent host —
your-store.myshopify.com, with nohttps://and no trailing path. Paperclip validates the format and rejects anything that is not amyshopify.comhost. - Finish setup.
Choose access
Because the endpoint is public, the connection grants no privileged reach: the boundary is the storefront itself. Connecting does not expose anything a shopper could not already find.
What does need attention is the write side. Cart and checkout operations are real actions against the store:
Warning:
cancel-cart,cancel-checkout, andcomplete-checkoutare classified destructive. Completing a checkout is a purchase. Leave these Off unless an agent genuinely needs them, and use Ask first at minimum.
Product and policy lookups are reads and are safe to leave Allowed. See Set action permissions.
One connection covers one store. Connect Shopify again for a second store.
Try it
Look up a product you can confirm on the storefront yourself:
Search the store for a product called "canvas tote" and tell me its price and whether it is in stock. Do not add anything to a cart.
Expect details matching the public product page. Keep the first check to a product or policy lookup — anything cart-related starts a real commerce flow.
Note: Illustrative task, not a recorded test result. Substitute a product from the store.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Setup fails with an authorization error | The storefront is not publicly reachable — it is password-protected, or the store is not on a plan that serves a public storefront | Confirm the storefront loads for a signed-out visitor. Making it public is a real commercial decision about your store, not a setup step to take lightly; if it should stay private, this connector is not usable for it |
| The store domain is rejected | A custom domain or a full URL was entered | Use the bare your-store.myshopify.com host |
| An agent cannot see orders or customers | Expected — this is not Admin API access | Nothing to fix here; this connector does not cover admin data |
| Products are missing from results | They are unpublished, or not available to the storefront's sales channel | Publish them in Shopify Admin |
| Policy search returns nothing | Policies are not filled in on the store | Add them in Shopify Admin |
| A checkout action unexpectedly completed | Checkout tools are real commerce actions | Set them to Off or Ask first |
Limitations: one store per connection, public storefront only, no Admin API. Shopify's own rate limits apply.
Related guides
- Stripe — payments data, with its own boundaries.
- Set action permissions
- How connector access works
- Shopify Storefront MCP documentation