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.8 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Sentry Connector | Let agents investigate Sentry errors, releases, and production issues. Organization and project reach, a safe read test, and troubleshooting. |
Sentry
Agents can investigate errors in Sentry — reading issues, stack traces, releases, and the context around a production problem.
This is a good connector to give a debugging agent, because the useful work is almost entirely reading.
Before you connect
- A Sentry account with access to the organization and projects you want agents to investigate.
- If your Sentry organization restricts third-party integrations, an administrator may need to approve the connection first.
Connect Sentry
- Open Connectors and select Sentry.
- On the Access step, choose the identity and which agents may use the connection.
- Complete Sentry's browser sign-in and choose the organization when prompted.
Paperclip registers its client with Sentry automatically, so there is nothing to configure in a developer console. This is the supported path and the one this page documents.
Choose access
Reach is the authorizing Sentry account's: the organization selected during sign-in, and the projects that account can see within it. Sentry's own team membership and role decide the rest.
Note: The connector's definition mentions organization, project, and environment scope, but those are descriptive — Paperclip does not enforce a project or environment filter on top of what Sentry grants. If an agent should only see one project, authorize with an account whose team membership is limited to it.
Most Sentry work is reading. Issue mutations — resolving, ignoring, assigning, deleting — change what your on-call engineers see, so keep them on Ask first or Off. An agent resolving an issue it misdiagnosed hides a live problem. See Set action permissions.
Warning: Stack traces and error context routinely contain user data, request payloads, and sometimes secrets that were logged by accident. An agent reading Sentry can surface those into a task transcript. Prefer Just agents I pick over Any agent for this connector.
Try it
Find the most frequent unresolved Sentry issue from the last 24 hours and summarize the error and where it happens. Do not resolve or assign anything.
Compare against the Sentry dashboard. Reading a known issue confirms the credential, the organization, and the agent's permission without changing your team's triage state.
Note: Illustrative task, not a recorded test result.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Authorization is refused or stays pending | The Sentry organization restricts third-party integrations | Ask a Sentry administrator to approve it |
| The connection is healthy but finds no issues | The wrong organization was selected during sign-in | Reconnect and choose the correct organization |
| Some projects are invisible | The authorizing account's team membership does not include them | Add the account to those teams in Sentry |
| An issue cannot be resolved by the agent | The action is Off, or the account's role does not permit it | Check the Permissions tab, then the Sentry role |
| An issue was resolved unexpectedly | A mutation was set to Allowed | Re-open it in Sentry and tighten the action settings |
| Needs attention | The grant expired or was revoked | Select Reconnect |
Limitations: one organization per connection. No project or environment filter inside Paperclip. Sentry's data retention bounds how far back an agent can look.
Related guides
- PagerDuty — incident response, often used alongside error tracking.
- Set action permissions
- How connector access works
- Sentry MCP server