← ClaudeAtlas

add-asanalisted

Add Asana project management MCP integration to Deus. Gives host-side Claude Code sessions read/write access to Asana tasks, projects, sections, and tags via @roychri/mcp-server-asana.
sliamh11/Deus · ★ 43 · AI & Automation · score 80
Install: claude install-skill sliamh11/Deus
# Add Asana This skill adds Asana project management tools to host-side Claude Code sessions via the `@roychri/mcp-server-asana` MCP server. Once installed, you can create/update tasks, manage projects and sections, search your workspace, add comments, and track task fields from conversation. This mirrors the `/add-linear` pattern: a local **stdio** server launched with `npx`, authenticated by an Asana **Personal Access Token (PAT)** sourced from `~/deus/.env`. The token never enters containers and is never copied into Claude Code's config. > Why not Asana's official MCP server? Asana's hosted MCP (`https://mcp.asana.com/v2/mcp`) is **OAuth-only** and Claude Code has no headless OAuth path (it requires browser consent and re-auth on token expiry), which breaks unattended host processes. The PAT-based community server is the right fit here. ## Phase 1: Pre-flight ### Check if already configured ```bash grep -q '"asana"' ~/.claude.json 2>/dev/null && echo "ALREADY_CONFIGURED" || echo "NOT_CONFIGURED" grep -q "ASANA_ACCESS_TOKEN" ~/deus/.env 2>/dev/null && echo "TOKEN_SET" || echo "NO_TOKEN" grep -q "READ_ONLY_MODE" ~/deus/.env 2>/dev/null && echo "READ_ONLY_ACTIVE" || echo "READ_WRITE" ``` - If both configured and token set, skip to Phase 3 (Verify). - If configured but no token, skip to Phase 2 step 1 only. - Otherwise, continue to Phase 2. ## Phase 2: Install and Configure ### Step 1: Get a Personal Access Token Tell the user: > I need an Asana Personal Access Toke