z4UjSpdZddlmZddlZddlZddlmZeejjjdz Z dZ e jr:e e ejvr"ejjde e ddl Z d dZd dZdddZdd Zddd Zd Zy#e$rdZ Y#wxYw)u/ Asana project management — in-process MCP so Jarvis runs Ahmed's projects by voice. THIN WRAPPER — deliberately. All the REST logic lives in ONE place, `jarvis-tools-service/asana.py`, which this module imports and re-exposes as in-process SDK-MCP tools. The hosted connector (mcp_server.py) wraps the SAME functions. So voice Jarvis and the claude.ai connector have IDENTICAL Asana capability, and one bug fix fixes both. Never re-implement a call here. Asana (app.asana.com) is where Ahmed's PROJECT work lives: projects, their tasks, due dates, assignees and comment threads. Distinct from mcp__tasks__* (his personal to-do list on the Railway brain). Auth: ASANA_PAT in .env, sent as `Authorization: Bearer `. MCP_ASANA=0 disables the whole server; a missing jarvis-tools-service dir just disables it too (enabled() returns False — the engine keeps booting). Optional ASANA_WORKSPACE (gid or name) pins the workspace. No extra deps — stdlib urllib. Everything a tool returns is SPOKEN ALOUD, so results are short plain prose / plain "- name — due …" lines. Never markdown, never a JSON dump, never a traceback: failures come back as one human sentence. (The one exception is asana_api, the escape hatch, whose raw JSON is for the model, not for speech.) Tools (Claude sees them as mcp__asana__): asana_workspaces list workspaces (and the default one) asana_projects list projects, optional name filter, optional archived asana_project_create new project (team needed only in an organization) asana_project_update rename / re-date / re-own / ARCHIVE (reversible) asana_project_members list, add or remove the people on a project asana_project_status post a status update (on_track / at_risk / …) asana_task FULL detail of one task (notes, section, subtasks, comments) asana_tasks open (or completed) tasks: a project, a section, or his own asana_task_create new task (project / section / parent / assignee / due date) asana_task_update rename, re-note, re-date, re-assign, (un)complete asana_task_move to another project and/or section (add + remove, a real move) asana_task_complete shortcut for "mark it done" asana_task_delete delete a task (recoverable for 30 days) asana_task_people assignee, followers, tags asana_subtasks list or create subtasks asana_comment post a comment asana_comments read the comment thread asana_search find tasks (premium search, typeahead fallback) asana_api escape hatch — any Asana REST endpoint ) annotationsN)Pathzjarvis-tools-servicectjjdddk(ryttxrt j S)zJOn when the shared module imported and a Personal Access Token is present. MCP_ASANA10F)osenvirongetboolasana configuredA/Users/ahmed/devFolder/Ultron/claude-voice/voice/asana_control.pyenabledr?s4 zz~~k3'3. ; -5++--rc$ddt|dgiS)Ncontenttext)typer)str)msgs r_textrFs S:; <   !%R RRrci}|jD]&\}}t|trd|fn|\}}||d||<(d|t|xsgdS)uA FULL JSON Schema for @tool. Why not the {"name": str} shorthand the SDK also accepts: it marks EVERY declared parameter as required, so `asana_projects` (all-optional) would be rejected with "'query' is a required property". A full schema (type + properties) is passed through verbatim, so we control `required` — and each property carries its own description, which is what the model actually reads. props: {name: "description"} → string, or {name: ("integer", "description")}. string)r descriptionobject)r propertiesrequired)itemsr(rlist)propsr1outkr*kinddescs r_schemar9Xs[C 1&0C&8h]a dt4ACT(.b=Q RRrc|ddlddlm}m}dfd |ddt idfd }|ddt d d d dfd }|d dt dddddddgdfd }|ddt ddddddddgdfd }|d!d"t dd#d$d%d&dgdfd' }|d(d)t dd*d+d,d-dd.gdfd/ }|d0d1t d2d3id2gdfd4 }|d5d6t d7d8d9d:d;dfd< } |d=d>t d?d@dAdBdCdDddEdgdfdF } |dGdHt d3ddddIdJdKdLd2gdfdM } |dNdOt d3dPdQdRdSd2gdfdT } |dUdVt d2d3id2gdfdW } |dXdYt d2d3id2gdfdZ }|d[d\t d3dJd]d^d_d`dad2gdfdb }|dcddt dedfdgd2gdfdh }|didjt d3dkdld2d.gdfdm }|dndot d3dpdqd2gdfdr }|dsdtt dudvdwdddxdydfdz }|d{d|t d}d~dddddgdfd }|dd|||||||| | | | | |||||||gS)Nr)create_sdk_mcp_servertoolc^Ktj|g|i|d{S7w)uEvery asana.* function is blocking and NEVER raises — it returns a sentence. Run it off the event loop and speak whatever comes back.N)r to_thread)fnakwasyncios r_runzbuild_server.._runss2,7,,R:!:r::;;:s -+ -asana_workspacesuList the Asana workspaces this account can see (and which one the other asana tools default to). Rarely needed — only for 'which Asana am I on' or when a project can't be found.cLKtjd{S7wr)r workspacesrrCs rrDz&build_server..asana_workspacesxs %**++++s $"$asana_projectszList Ahmed's Asana projects. `query` optionally narrows by name ('redesign', 'client'). `archived`='true' lists archived ones instead. Use for 'what projects do I have', 'what's in Asana'.z(a word or two to narrow the list by name)booleanz%true = list ARCHIVED projects instead)queryarchivedc Ktjt|dtt |dd{S7w)NrJrK)r projectsr r r+rGs rrHz$build_server..asana_projectss>%.."T7*;r$ 3466 66s9AAAasana_project_createzCreate an Asana project. `name` required. `team` is only needed if the workspace is an ORGANIZATION (the tool tells you, and lists the teams, if so). Optional `notes`, `due_on` (YYYY-MM-DD), `privacy` (public_to_workspace | private_to_team | private).zthe project namez(only needed in an ORGANIZATION workspacezdescription of the projectz YYYY-MM-DDz/public_to_workspace | private_to_team | private)nameteamnotesdue_onprivacyrOc Ktjt|dt|dt|dt|dt|dd{S7w)NrOrPrQrRrS)r project_creater rGs rrNz*build_server..asana_project_createsZ%..40@"T6BRT7+Rh-?D)ATVV VVsAAAAasana_project_updateu1Change an Asana project (`project` = its name or gid): `name` (rename), `notes`, `due_on`, `owner`, or `archive`='true' to ARCHIVE it (hides it, keeps everything, reversible with archive='false'). Archiving is how you 'get rid of' a project — deleting one is NOT offered here because it can't be undone.zthe project's name or gidza new name (rename)znew descriptionz new owner: a name, email or 'me')rIz%true = archive it, false = un-archive)projectrOrQrRownerarchiverWc Ktjt|dt|dt|dt|dt|dt|dd{S7w)NrWrOrQrRrXrY)r project_updater r+rGs rrVz*build_server..asana_project_updates`%..40CRfEUT7+Rh-?D'ART9-// //AA&A$ A&asana_project_membersuWho's on a project — and invite/remove them ('add Sara to the launch project'). `add` / `remove` = comma-separated emails, names or gids ('me' works). `access_level` (admin|editor|commenter|viewer) sets their rights when adding. No add/remove = just list the members. NOTE: this shares an existing project with someone already in the workspace; inviting a brand-new person to Asana itself is asana_api POST /workspaces/{gid}/addUser.z9comma-separated people to add (emails, names, gids, 'me')z comma-separated people to removez#admin | editor | commenter | viewer)rWaddremove access_levelc Ktjt|dt|dt|dt|dd{S7w)NrWr^r_r`)r project_membersr rGs rr]z+build_server..asana_project_memberssP%//D)1DbuoT8,b~.FHH HHAA A Aasana_project_statuszPost a status update on a project so the team sees where it stands. `text` = the update. `status_type` = on_track (default), at_risk, off_track, on_hold, or complete. `title` optional.zthe status update itselfz=on_track (default) | at_risk | off_track | on_hold | completezoptional headline)rWr status_typetitlerc Ktjt|dt|dt|ddt|dd{S7w)NrWrreon_trackrf)r project_statusr rGs rrdz*build_server..asana_project_statussS%..40CRfEUT=*=r$?PRR RRAA A A asana_taskzFULL detail of ONE Asana task (`task` = its name or gid): notes, assignee, due date, project, section, tags, followers, subtasks and the latest comments. Use it for 'tell me about that task', 'what's the story on X', or before changing something.taskzthe task's name or gidcbKtjt|dd{S7wNrl)r rlr rGs rrkz build_server..asana_tasks'%**bv&67777 %/-/ asana_taskszList Asana tasks. `project` (name or gid) = that project's tasks; add `section` for one board column; no project = Ahmed's OWN tasks ('what's on my plate'). Open tasks only unless `completed`='true'. `limit` defaults to 50.z0a project name or gid; empty = Ahmed's own tasksz"a board column inside that project)rIz#true = list COMPLETED tasks instead)integerz max tasks to return (default 50))rWsection completedlimitc Kt|d}tj|| t|dtt |dt |j dxsdd{S7w)NrWrrrsrt2)r r tasksr r+intr )rprojrCs rrpz!build_server..asana_taskssf$ "%++tXr$ 7Jr$ 45dhhw/52688 88sA%A/(A-)A/asana_task_createuCreate an Asana task. `name` (short, imperative) is required. `project` = the project name/gid to file it under (without one it lands in his My Tasks). `section` = the board column inside that project. `parent` = another task, to make this a SUBTASK of it. `notes` = detail. `assignee` = a person's name/email, or 'me' (the default). `due_on` = YYYY-MM-DD — resolve 'tomorrow' / 'next Thursday' to a real date yourself (Asia/Riyadh).z!the task name (short, imperative)z$project name or gid to file it underz board column inside that projectu+another task — makes this a SUBTASK of itzdetail / descriptionz+a person's name or email, or 'me' (default))rOrWrrparentrQassigneerRc Ktjt|dt|dt|dt|ddt|dt|dt|dd{S7w) NrOrQrWr|merRrrr{)r task_creater rGs rrzz'build_server..asana_task_createso %++Rf-=r$?PT9-r$ D/IT8,by.A2dHCUWW WWsA(A2+A0,A2asana_task_updateuChange an existing Asana task (`task` = its gid or name, matched fuzzily). Set only what changes: `name` (rename), `notes`, `due_on` (YYYY-MM-DD), `start_on` (needs a due date too, and a PAID Asana plan — it fails on his free one), `assignee` (a name or 'me'), `complete` ('true' to close, 'false' to reopen). Use for 'push that to Friday', 'give it to Sara', 'reopen the launch task'.zYYYY-MM-DD (paid plans only)z!a person's name or email, or 'me')rIztrue = close it, false = reopen)rlrOrQrRstart_onr|r'c Ktjt|dt|dt|dt|dt|dt|dt|dd{S7w)NrlrOrQrRrr|r')r task_updater r+rGs rrz'build_server..asana_task_updatesm%++Rf-=r$?OT7+Rh-?D*AUT:.40DFF FFsA'A1*A/+A1asana_task_moveukMove a task to another `project` and/or `section` (board column). This is a REAL move — the task is taken out of the project it was in (Asana would otherwise leave it in both). `section` alone moves it between columns of its current project. `remove_from` optionally names just one project to drop. Use for 'move it to Done', 'that belongs on the client board'.zthe project to move it INTOzthe board column to put it inz+optionally, the one project to drop it from)rlrWrr remove_fromc Ktjt|dt|dt|dt|dd{S7w)NrlrWrrr)r task_mover rGs rrz%build_server..asana_task_movesO%//2dF+;Ri=PT9-r$ /FHH HHrcasana_task_completez{Mark an Asana task done. `task` = its gid or name. Use for 'tick off the landing page task', 'that Asana task is finished'.cbKtjt|dd{S7wrn)r task_completer rGs rrz)build_server..asana_task_completes) %--r$/?@@@@roasana_task_deleteuDelete an Asana task ('remove that task', 'get rid of it'). It goes to Asana's Deleted Items and can be restored for 30 days, so it's safe — but only do it when he clearly means DELETE, not 'mark it done' (asana_task_complete).cbKtjt|dd{S7wrn)r task_deleter rGs rrz'build_server..asana_task_deletes)%++Rf-=>>>>roasana_task_peopleuWho and what is on a task: set the `assignee`, add/remove followers (`add_followers` / `remove_followers`, comma-separated names, emails or 'me'), add/remove tags (`add_tag` / `remove_tag` — a new tag is created if it doesn't exist). With no changes it just reports who's on it.z*comma-separated people to add as followersz#comma-separated people to un-followz%comma-separated tags (created if new)zcomma-separated tags to remove)rlr| add_followersremove_followersadd_tag remove_tagc Ktjt|dt|dt|dt|dt|dt|dd{S7w)Nrlr|rrrr)r task_peopler rGs rrz'build_server..asana_task_people#se%++Rf-=r$ ?ST?3R>P5QT9-r$ /EGG GGr\asana_subtaskszList a task's subtasks, or create them: `add` = comma-separated subtask names ('draft the copy, get sign-off'). Use for 'break that task down'.zthe parent task's name or gidz'comma-separated subtask names to create)rlr^cxKtjt|dt|dd{S7w)Nrlr^)r subtasksr rGs rrz$build_server..asana_subtasks4s/%.."T6*:BtUOLLLL 0:8: asana_commentzAdd a comment to an Asana task so the team sees it. `task` = its gid or name, `text` = the comment. Use for 'comment on the design task that the client approved'.z the comment)rlrcxKtjt|dt|dd{S7w)Nrlr)r commentr rGs rrz#build_server..asana_comment=s0%--D&)92dF;KLLLLrasana_commentsuREAD the comment thread on a task (system events are skipped) — 'what did they say on that task', 'any update from the team'. `limit` = how many of the latest to show (default 10).)rqz#how many of the latest (default 10))rlrtc Ktjt|dt|j dxsdd{S7w)Nrlrt )r commentsr rxr rGs rrz$build_server..asana_commentsFsE%.."T6*:dhhw/52688 88sAA A A  asana_searchuFind Asana tasks when you don't know where they live ('find the invoice task', 'anything about the Riyadh launch'). `query` = a word or two; optional filters `project`, `assignee` ('me' or a name), `due_before` / `due_after` (YYYY-MM-DD), `completed` ('true'/'false'). On a free Asana plan it falls back to name matching (descriptions aren't searched), and the index lags up to a minute — for a task you JUST created use asana_task / asana_tasks instead.za word or two to look forz"limit to one project (name or gid)z'me' or a person's name)rIz#true = only done, false = only open)rJrWr| due_before due_afterrsc Ktjt|dt|dt|dt|dt|dt|dd{S7w)NrJrWr|rrrs)r searchr r+rGs rrz"build_server..asana_searchQsb%,,4(92dI;NT:.40FT;/D+1FHH HHr\ asana_apiuEscape hatch — call ANY Asana REST endpoint (base https://app.asana.com/api/1.0) for things the other asana tools don't cover: sections, tags, teams, attachments, dependencies, templates, goals, portfolios, custom fields, webhooks, inviting a NEW person to the workspace, deleting a project. `method` = GET/POST/PUT/DELETE, `path` = everything after /api/1.0 (e.g. '/projects/123/sections'). Do NOT wrap `body_json` in {"data":…} — that's added for you. IMPORTANT: Asana returns only gid/name unless you ask for fields, so pass e.g. params_json={"opt_fields":"name,due_on,assignee.name","limit":50}. Returns raw JSON — summarise it, never read it out.zGET | POST | PUT | DELETEz6everything after /api/1.0, e.g. /projects/123/sectionsu+JSON body, WITHOUT the {"data":…} wrapperu)JSON query params — put opt_fields here)methodpath body_json params_jsonrrc Ktjt|ddt|dt|dt|dd{S7w)NrGETrrr)r rawr rGs rrzbuild_server..asana_apicsQ"%))Rh%>4@PT;/D-1HJJ JJrjr z2.0.0)rOversiontools)returndict)rrrr)rBclaude_agent_sdkr;r<r9)r;r<rDrHrNrVr]rdrkrprzrrrrrrrrrrrCrBs @@r build_serverrns8<<   ./6r{<, <,  B FSU V W 6 W 6  ? -E8)O Q (   V V   90;L)4VRT+    /  /  ! ' 9U?#HJ+    H  H  ? 95"a/1f%  ' (R(R , 1 634vh ? A 8 A 8 -  PB RKM N O8O8   X >D@J2L) +( WW   J 30;L)7UBM O (   F F   Q 3;="OQ(   H H  ? 634vh ?AA AA  # 634vh ? A ? A ?  O 3B$P'LE!A C (   G G   T :CE(  M  M /  3]K6" $ % M % M  - 3NP(  88 . . 7B8!-L R T U VH VH  + B 8S O"MOV$  &' J!' J ! g1E#%:rs*V#  > ! ! # * * 1 14J J  x= ( HHOOAs8} - .=:SS,Qg EsA B++B54B5