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 |
|---|---|
| Asana Connector | Let agents read and update Asana tasks. Registering the required OAuth app, workspace and project reach, a read test, and troubleshooting. |
Asana
Agents can work with Asana tasks — finding them, reading details, and updating or creating them.
Before you connect
- An Asana account with access to the workspace and projects you want agents to use.
- You must register your own Asana OAuth app. Asana does not support automatic client registration for this server, so there is no path that skips the developer console. Add Paperclip's callback URI to the app; Paperclip shows the exact URI during setup.
- Some Asana organizations restrict who may create or authorize apps. If you are not an administrator, check before you start rather than after.
Connect Asana
The callback URI comes from Paperclip and the client credentials come from Asana, so the two consoles interleave. Open Paperclip's setup first to read the URI, then register the app, then come back.
1. Read Paperclip's callback URI
- Open Connectors and select Asana.
- On the Access step, choose the identity and which agents may use the connection.
- Select Use your own OAuth app. Paperclip displays the exact callback URI — copy it. It is the
/api/tools/oauth/callbackroute on your instance's origin. Leave this screen open.
2. Create the Asana MCP app
In Asana's developer console at app.asana.com/0/my-apps:
- Select Create new app and enter a name.
- Set the app type to "MCP app". This is the step that catches people out — a standard API app will not work here, because Asana keeps MCP tokens separate.
- Select Create app.
- In the OAuth section of the sidebar, add the callback URI from step 1 as the Redirect URL.
- Under Manage distribution, choose the specific workspaces the app may be used in, or allow any workspace.
- Copy the client ID and client secret.
Note: Asana MCP apps have no scopes to choose. Asana's guidance is to use
defaultor omit the parameter entirely — so if you are looking for a permissions checklist here, there is not one. Reach comes from the authorizing account instead.
3. Finish in Paperclip
Return to the setup screen, supply the client ID and secret, then authorize in Asana as the account whose access you want the connection to have.
Asana's own reference is Integrating with Asana's MCP server.
Choose access
Reach is the authorizing Asana account's: the workspaces it belongs to and the projects it can open. Private projects the account is not a member of stay invisible, which is often the simplest way to keep something out of reach.
There is no workspace or project picker in Paperclip. To narrow access, authorize with an account that is a member of fewer projects.
Task creation, updates, and comments are writes that your team will see. Leave them on Ask first until the workflow is proven. Reads can stay Allowed. See Set action permissions.
Attribution follows the authorizing account, so a dedicated account makes agent activity distinguishable. See Use separate accounts for people and agents.
Try it
Find the Asana task called "Update onboarding checklist" and tell me its assignee, due date, and current status. Do not change it.
Compare against the task in Asana. A lookup of a task you can already see confirms the credential and the agent's permission without touching your team's board.
Note: Illustrative task, not a recorded test result. Substitute a task name from your own workspace.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Setup asks for a client ID and secret | Expected — Asana requires your own OAuth app | Register one in Asana's developer console |
| Authorization fails with a redirect or URI error | The callback URI on the Asana app does not match the one Paperclip shows | Copy the URI exactly and retry |
| You cannot create the app | The Asana organization restricts app creation | Ask an Asana administrator |
| A project's tasks are invisible | The authorizing account is not a member of that project | Add it to the project in Asana; no reconnect needed |
| An update is rejected | Asana's own field rules or permissions on that project | Check the task and project settings in Asana |
| Needs attention | The grant was revoked in Asana | Select Reconnect |
Limitations: one Asana account per connection. No workspace or project restriction inside Paperclip. Asana's rate limits apply.
Related guides
- Jira, Linear, Todoist — other work tracking connectors.
- Use separate accounts for people and agents
- Set action permissions
- Asana MCP server documentation