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.4 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Box Connector | Let agents search and read Box content. The Box administrator work required first, enterprise limits, a read test, and troubleshooting. |
Box
Agents can search and work with files and folders in Box.
Warning: This connector needs Box administrator work before anyone can connect. An administrator creates the OAuth integration in Box and enables AI access for the enterprise. Without both, authorization either fails or succeeds into an empty account.
Before you connect
- A Box administrator who will create the OAuth integration and enable AI access for the enterprise. If that is not you, start by asking them — no amount of work in Paperclip substitutes for it.
- The client ID and secret from that Box integration, and Paperclip's callback URI registered on it. Paperclip shows the URI during setup.
- A Box account with access to the content you want agents to use.
Box does not support automatic client registration for this server, so your own OAuth integration is required rather than optional.
Connect Box
Most of this happens in Box's Admin Console and needs an administrator. Start in Paperclip only to read the callback URI.
1. Read Paperclip's callback URI
Open Connectors → Box → the Access step → Use your own OAuth app. Paperclip displays the callback URI; copy it and give it to whoever does step 3.
2. Turn on Box AI for the enterprise
In the Box Admin Console:
- Select Box AI, then Settings.
- Ensure AI API is enabled.
- Ensure Official Box Integrations is enabled for all users is selected.
Warning: Without these, authorization can succeed and still leave agents unable to do anything useful. If the connection looks healthy but every call fails or returns nothing, come back to this step before debugging anything in Paperclip.
3. Create the integration credentials
Still in the Admin Console:
- Select Integrations in the left sidebar.
- Filter by the MCP category, or search for the Box MCP server you want.
- Beside the selected MCP server, select its state and enable it.
- For a server that is not listed, hover over Custom Box MCP Server and select Configure.
- Under Additional Configuration, select + Add Integration Credentials.
- Copy the generated Client ID and Client Secret.
- Enter the Redirect URI from step 1.
- Under Scopes, ensure Manage AI is selected.
4. Finish in Paperclip
Return to the setup screen, supply the client ID and secret, then authorize in Box as the account whose content the agents should reach.
Box's own reference is Managing Box MCP Servers.
Choose access
Reach is the authorizing Box account's: the files, folders, and shared content that account can already open. Paperclip has no folder picker, so narrow access by authorizing with an account that has access to less.
Box enterprises often apply further restrictions on top — classification labels, shared-link policies, and app-access rules can all keep content out of an integration even when the user can see it in the Box web app. This is the usual reason an agent finds nothing after an apparently clean setup.
File writes and deletions are consequential and not always recoverable from Paperclip. Leave them on Ask first or Off, and rely on Box's trash and version history for recovery. See Set action permissions.
Try it
Search Box for a file named "supplier agreement" and tell me its folder and last modified date. Do not download, move, or change anything.
Compare against Box. A metadata read confirms the credential and the enterprise's AI access without pulling document contents into a task transcript.
Note: Illustrative task, not a recorded test result. Substitute a filename you can find yourself.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Authorization fails | The Box OAuth integration does not exist, or the callback URI does not match | Have an administrator create it and register the exact URI |
| Authorization succeeds but nothing is found | AI access is not enabled for the enterprise, or an enterprise policy blocks the app | Ask a Box administrator to enable AI access and check app-access rules |
| Some folders are visible and others are not | The authorizing account is not a collaborator on them, or classification rules apply | Add the account as a collaborator, or check the classification policy |
| A file cannot be read despite being listed | Enterprise restrictions on that content, or an unsupported file type | Check the file's classification in Box |
| A delete or move happened unexpectedly | A write action was set to Allowed | Restore from Box trash, then tighten the action settings |
| Needs attention | The grant was revoked, or the integration was disabled | Select Reconnect; check the integration still exists |
Limitations: one Box account per connection. No folder restriction inside Paperclip. Enterprise policy can override what the account appears to have.
Related guides
- Google Drive — another file storage connector.
- Set action permissions
- How connector access works
- Managing Box MCP servers