create asana mcp server guide

[walker-tx]

Use the following URL: https://mcp.asana.com/v2/mcp

[walker-tx]

guide:draft run failed.

(no reason file written; check workflow logs)

Workflow run: https://github.com/speakeasy-api/mcp-setup-docs/actions/runs/30045451409

Re-add guide:draft to retry after clarifying or fixing.

[walker-tx]

Resolved as asana (Asana), persona it-admin.

Notes handed to the pipeline:

MCP endpoint: https://mcp.asana.com/v2/mcp

Starting draft-guide…

[walker-tx]

guide:draft run failed.

draft-guide exited 2 (see workflow logs). Converged drafts still open a PR; unconverged/blocked/failed fail the job.

Workflow run: https://github.com/speakeasy-api/mcp-setup-docs/actions/runs/30045655200

Re-add guide:draft to retry after clarifying or fixing.

[walker-tx]

Manual backfill from run 30045655200 (files were discarded; factory will comment this automatically after the next merge).

Pipeline review (asana)

Status: unconverged after 3 review round(s).

Unresolved blockers (3)

These need a human call (live console check, drop the branch, or supply exact UI labels).

• fidelity · #copy-client-credentials (research)
  • The Dossier still does not identify the destructive confirmation control or where the replacement Client secret appears, yet setup relies on both details.
  • Suggestion: Verify the authenticated reset flow and document the exact confirmation label, replacement-secret location, and copy-and-store sequence — or drop the secret-reset recovery branch from setup.
• achievability · #copy-client-credentials (research)
  • The secret-reset recovery still omits the confirmation control's exact label, the replacement secret's display location, and the exact Control Plane path for replacing the stored secret.
  • Suggestion: Verify and document the complete reset flow, or remove that recovery path until verified.
• achievability · #allow-app-access — “To reverse an explicit block” (setup)
  • The explicit-block branch tells the administrator to open Connected apps without explaining how to reach it.
  • Suggestion: Add: profile photo > Admin console > Apps > Manage apps > Connected apps, then select the app and Unblock — or drop the unblock branch.

Open questions (4)

• Exact OAuth Redirect URL save control is undocumented.
• Client secret persistence after leaving creation is undocumented.
• Exact app-name field label is undocumented.
• Speakeasy catalog presence was not verified.

How to clarify / retry

1. Reply on this issue with answers (exact button labels, nav paths, or “drop the secret-reset recovery branch”).
2. Optionally edit the issue body with the same facts.
3. Re-add the guide:draft label. Distill will read the body and issue comments into --notes.

Source: tmp.1Tj2Sn1mVx

[walker-tx]

Plain English (Asana run)

The draft guide includes a “what if you lose the Client secret” recovery path (reset/regenerate it in Asana’s developer console). Reviewers blocked that because:

1. Public Asana docs don’t say the exact button label on the “are you sure?” confirm dialog after Reset, or where the new secret appears on screen afterward.
2. Without those labels, an IT admin following the guide cold would have to guess on a destructive action (rotating a secret).
3. Separately, an “unblock a blocked app” branch says “open Connected apps” without the click path to get there.

You don’t need to read the whole guide. Pick one reply style per decision (after #9 merges, the factory will ask this way automatically):

• Decision 1: drop this branch — remove secret-reset recovery until someone verifies it in a real Asana org
• Decision 1: verified — confirm button is "**…**"; new secret shows under "**…**"
• Same for the unblock path (Decision 2: drop or verified — nav is …)

Open questions (same idea — unknown UI chrome): OAuth redirect save control, whether the secret survives leaving the create screen, exact app-name field label, whether Asana is in the Speakeasy catalog.

[walker-tx]

Plain English (Asana run)

The draft guide includes a “what if you lose the Client secret” recovery path (reset/regenerate it in Asana’s developer console). Reviewers blocked that because:

1. Public Asana docs don’t say the **exact button label** on the “are you sure?” confirm dialog after Reset, or **where the new secret appears** on screen afterward.

2. Without those labels, an IT admin following the guide cold would have to guess on a **destructive** action (rotating a secret).

3. Separately, an “unblock a blocked app” branch says “open Connected apps” without the click path to get there.

This “what if you lose the Client secret” should not be included in the guide. We do not cover contingencies or user errors like this.