com.mcparmory/asana
OCI · GHCR.IO/MCPARMORY/ASANA:1.0.5 · 2 COMPONENTS · SCANNED SEP 20
Manage tasks, projects, portfolios, and team workflows
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 25088 tokens (~114/item across 220 items; 220 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 36 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 220 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/asana MCP server?
com.mcparmory/asana runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/asana:1.0.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/asana:1.0.5
claude mcp add com-mcparmory-asana -- docker run --rm -i ghcr.io/mcparmory/asana:1.0.5
{
"mcpServers": {
"com-mcparmory-asana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/asana:1.0.5"
]
}
}
} {
"servers": {
"com-mcparmory-asana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/asana:1.0.5"
]
}
}
} codex mcp add com-mcparmory-asana -- docker run --rm -i ghcr.io/mcparmory/asana:1.0.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-asana": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/asana:1.0.5"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-asana:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/asana:1.0.5"] {
"McpServers": {
"com-mcparmory-asana": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/asana:1.0.5"
]
}
}
} {
"mcpServers": {
"com-mcparmory-asana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/asana:1.0.5"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/asana:1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_custom_field_to_goal Add Custom Field to Goal ~201
Associates a custom field with a goal by creating a custom field setting, allowing the field to appear and be tracked on the specified goal.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_field | – | yes | The globally unique identifier of the custom field to associate with the goal. |
| goal_gid | string | yes | The globally unique identifier of the goal to which the custom field setting will be added. |
| insert_after | string | – | The GID of an existing custom field setting on this goal after which the new custom field setting will be inserted to control display order. Cannot be used together with insert_before. |
| insert_before | string | – | The GID of an existing custom field setting on this goal before which the new custom field setting will be inserted to control display order. Cannot be used together with insert_after. |
| is_important | boolean | – | When set to true, marks this custom field as important for the goal, causing it to be prominently displayed in list views of the goal. |
No output schema declared.
No examples provided.
add_custom_field_to_portfolio Add Custom Field to Portfolio ~226
Associates a custom field with a portfolio by creating a custom field setting, allowing the field to appear and be tracked within the portfolio. Optionally controls the display prominence and ordering of the field relative to other custom field settings on the portfolio.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_field | – | yes | The globally unique identifier (GID) of the custom field to associate with the portfolio. |
| insert_after | string | – | The GID of an existing custom field setting on this portfolio after which the new custom field setting will be inserted to control ordering. Cannot be used together with insert_before. |
| insert_before | string | – | The GID of an existing custom field setting on this portfolio before which the new custom field setting will be inserted to control ordering. Cannot be used together with insert_after. |
| is_important | boolean | – | When set to true, marks this custom field as important for the portfolio, causing it to be prominently displayed in list views of the portfolio's items. |
| portfolio_gid | string | yes | The globally unique identifier of the portfolio to which the custom field setting will be added. |
No output schema declared.
No examples provided.
add_custom_field_to_project Add Custom Field to Project ~213
Associates a custom field with a project by creating a custom field setting, allowing the field to appear and be used within that project. Optionally controls the field's display prominence and its position relative to other custom field settings.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_field | – | yes | The globally unique identifier (GID) of the custom field to associate with the project. |
| insert_after | string | – | The GID of an existing custom field setting on this project after which the new setting will be inserted to control ordering. Cannot be used together with insert_before. |
| insert_before | string | – | The GID of an existing custom field setting on this project before which the new setting will be inserted to control ordering. Cannot be used together with insert_after. |
| is_important | boolean | – | When true, marks this custom field as important for the project, causing it to be prominently displayed in list views of the project's items. |
| project_gid | string | yes | The unique identifier of the project to which the custom field will be added. |
No output schema declared.
No examples provided.
add_goal_followers Add Goal Followers ~105
Adds one or more followers (collaborators) to a specified goal. Returns the complete updated goal record reflecting the new followers.
| Name | Type | Req | Description |
|---|---|---|---|
| followers | array | yes | A list of users to add as followers to the goal. Each item can be the string 'me' to reference the authenticated user, a user's email address, or a user's GID. Order is not significant. |
| goal_gid | string | yes | The unique identifier of the goal to which followers will be added. |
No output schema declared.
No examples provided.
add_goal_supporting_relationship Add Goal Supporting Relationship ~264
Links a supporting resource (goal, project, task, or portfolio) to a parent goal, establishing a progress relationship between them. Returns the newly created goal relationship record.
| Name | Type | Req | Description |
|---|---|---|---|
| contribution_weight | number | – | A weight between 0 and 1 (inclusive) that determines how much the supporting resource's progress contributes to the parent goal's overall progress. Must be greater than 0 for the supporting resource… |
| goal_gid | string | yes | The unique identifier of the parent goal to which the supporting resource will be linked. |
| insert_after | string | – | The GID of an existing subgoal of the parent goal; the new subgoal will be inserted immediately after it. Cannot be used together with `insert_before`. Only supported when adding a subgoal. |
| insert_before | string | – | The GID of an existing subgoal of the parent goal; the new subgoal will be inserted immediately before it. Cannot be used together with `insert_after`. Only supported when adding a subgoal. |
| supporting_resource | string | yes | The unique identifier of the resource to add as a supporting relationship to the parent goal. Must be the GID of a goal, project, task, or portfolio. |
No output schema declared.
No examples provided.
add_portfolio_item Add Portfolio Item ~143
Adds a project or item to a specified portfolio, optionally controlling its position relative to an existing item. Returns an empty data block on success.
| Name | Type | Req | Description |
|---|---|---|---|
| insert_after | string | – | The ID of an existing portfolio item after which the new item will be inserted. Cannot be used together with insert_before. |
| insert_before | string | – | The ID of an existing portfolio item before which the new item will be inserted. Cannot be used together with insert_after. |
| item | string | yes | The globally unique identifier of the project or item to add to the portfolio. |
| portfolio_gid | string | yes | The globally unique identifier of the portfolio to which the item will be added. |
No output schema declared.
No examples provided.
add_portfolio_members Add Portfolio Members ~106
Adds one or more users as members of the specified portfolio, granting them access to view and collaborate on it. Returns the updated portfolio record.
| Name | Type | Req | Description |
|---|---|---|---|
| members | string | yes | A comma-separated list of user identifiers to add as portfolio members; each identifier can be the string 'me', a user's email address, or a user's globally unique identifier (gid). Order is not sign… |
| portfolio_gid | string | yes | The globally unique identifier of the portfolio to which members will be added. |
No output schema declared.
No examples provided.
add_project_followers Add Project Followers ~100
Adds one or more users as followers to a project, automatically making them members if they are not already. Followers receive 'tasks added' notifications for the project.
| Name | Type | Req | Description |
|---|---|---|---|
| followers | string | yes | A comma-separated list of user identifiers to add as followers; each identifier can be the string 'me', a user's email address, or a user's GID. |
| project_gid | string | yes | The unique identifier of the project to which followers will be added. |
No output schema declared.
No examples provided.
add_project_members Add Project Members ~99
Adds one or more users as members of the specified project. Note that added members may also become followers depending on their personal notification settings.
| Name | Type | Req | Description |
|---|---|---|---|
| members | string | yes | A comma-separated list of user identifiers to add as project members. Each identifier can be the string 'me', a user's email address, or a user's globally unique identifier (gid). |
| project_gid | string | yes | The globally unique identifier of the project to which members will be added. |
No output schema declared.
No examples provided.
add_task_comment Add Task Comment ~154
Adds a comment story to a task, authored by the currently authenticated user and timestamped at the time of the request. Returns the full record of the newly created story.
| Name | Type | Req | Description |
|---|---|---|---|
| is_pinned | boolean | – | Whether the story should be pinned to the top of the task's story feed, making it prominently visible. |
| sticker_name | string | – | The name of the sticker to attach to this story. Omit or set to null if no sticker is desired. |
| task_gid | string | yes | The unique identifier (GID) of the task to which the story will be added. |
| text | string | – | The plain text content of the comment to post on the task. Cannot be used together with html_text. |
No output schema declared.
No examples provided.
add_task_dependencies Add Task Dependencies ~106
Marks one or more tasks as dependencies of a specified task, establishing that the target task depends on their completion. A task may have at most 30 dependents and dependencies combined.
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | – | An array of task GIDs to mark as dependencies of the specified task; order is not significant and each item should be a valid task GID string. |
| task_gid | string | yes | The unique identifier (GID) of the task to which dependencies will be added. |
No output schema declared.
No examples provided.
add_task_dependents Add Task Dependents ~116
Marks one or more tasks as dependents of the specified task, meaning those tasks depend on this task being completed. A task can have at most 30 dependents and dependencies combined.
| Name | Type | Req | Description |
|---|---|---|---|
| dependents | array | – | An array of task GIDs to mark as dependents of the specified task. Order is not significant; each item should be a valid task GID string. |
| task_gid | string | yes | The unique identifier of the task that will become the dependency (i.e., the task that others will depend on). |
No output schema declared.
No examples provided.
add_task_followers Add Task Followers ~104
Adds one or more followers to a specified task, associating them with it for updates and visibility. Returns the complete updated task record upon success.
| Name | Type | Req | Description |
|---|---|---|---|
| followers | array | yes | A list of users to add as followers, where each entry can be the string 'me', a user's email address, or a user's GID. Order is not significant. |
| task_gid | string | yes | The unique identifier (GID) of the task to which followers will be added. |
No output schema declared.
No examples provided.
add_task_tag Add Tag to Task ~84
Adds an existing tag to a specified task, associating them for organization and filtering purposes. Returns an empty data block on success.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | yes | The unique global identifier (GID) of the tag to attach to the task. |
| task_gid | string | yes | The unique global identifier (GID) of the task to which the tag will be added. |
No output schema declared.
No examples provided.
add_task_to_project Add Task to Project ~302
Adds a task to a specified project, optionally positioning it relative to another task or within a section. Can also be used to reorder a task already in the project; a task may belong to at most 20 projects.
| Name | Type | Req | Description |
|---|---|---|---|
| insert_after | string | – | The GID of an existing task in the project after which this task should be inserted. Pass null to place the task at the beginning of the list or, when combined with `section`, at the beginning of tha… |
| insert_before | string | – | The GID of an existing task in the project before which this task should be inserted. Pass null to place the task at the end of the list or, when combined with `section`, at the end of that section.… |
| project | string | yes | The unique identifier of the project to add the task to. |
| section | string | – | The GID of a section within the project into which the task should be placed. By default the task is added to the end of the section; combine with `insert_after: null` to place at the beginning, `ins… |
| task_gid | string | yes | The unique identifier of the task to add to the project. |
No output schema declared.
No examples provided.
add_task_to_section Add Task to Section ~179
Moves a task into a specific section within a project, removing it from any other sections. The task is placed at the top of the section by default, or at a specific position using insert_before or insert_after.
| Name | Type | Req | Description |
|---|---|---|---|
| insert_after | string | – | The unique identifier of an existing task in this section after which the added task should be inserted. Mutually exclusive with insert_before. |
| insert_before | string | – | The unique identifier of an existing task in this section before which the added task should be inserted. Mutually exclusive with insert_after. |
| section_gid | string | yes | The unique identifier of the section to which the task will be added. |
| task | string | – | The unique identifier of the task to add to the section. Note: tasks with a resource_subtype of 'section' (separators) are not supported. |
No output schema declared.
No examples provided.
add_team_member Add Team Member ~113
Adds a user to the specified team, creating a new team membership record. The requesting user must already be a member of the team, and the user being added must belong to the same organization.
| Name | Type | Req | Description |
|---|---|---|---|
| team_gid | string | yes | The unique identifier of the team to which the user will be added. |
| user | string | – | The identifier of the user to add to the team — accepts the literal string 'me' for the current user, a user's email address, or a user's globally unique identifier (GID). |
No output schema declared.
No examples provided.
add_workspace_user Add Workspace User ~94
Adds a user to a workspace or organization by user ID or email address. Returns the full user record for the newly added user.
| Name | Type | Req | Description |
|---|---|---|---|
| user | string | – | The identifier of the user to add, accepted as the literal string 'me' (current user), an email address, or a user GID. |
| workspace_gid | string | yes | The unique identifier of the workspace or organization to which the user will be added. |
No output schema declared.
No examples provided.
approve_access_request Approve Access Request ~58
Approves a pending access request, granting the requester access to the associated target object. Use this to fulfill access requests that have been reviewed and authorized.
| Name | Type | Req | Description |
|---|---|---|---|
| access_request_gid | string | yes | The globally unique identifier of the access request to approve. |
No output schema declared.
No examples provided.
create_allocation Create Allocation ~46
Creates a new allocation and returns the full record of the newly created allocation.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The allocation data to create, including all relevant fields for the new allocation record. |
No output schema declared.
No examples provided.
create_budget Create Budget ~70
Creates a new budget with the specified configuration. Use this to define spending limits and tracking parameters for a project, team, or time period.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The budget object containing all required fields to define the new budget, such as name, amount, currency, and associated scope or time period. |
No output schema declared.
No examples provided.
create_custom_field Create Custom Field ~99
Creates a new custom field within a specified workspace, supporting types such as text, enum, multi_enum, number, date, or people. The field name must be unique within the workspace and cannot conflict with existing task property names.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The request body containing the custom field definition, including required properties such as workspace, name, and type (one of: text, enum, multi_enum, number, date, or people). |
No output schema declared.
No examples provided.
create_enum_option Create Enum Option ~110
Creates a new enum option and appends it to the specified custom field's list of selectable values. A custom field supports up to 500 enum options (including disabled ones); locked fields can only be modified by the user who locked them.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_field_gid | string | yes | The globally unique identifier of the custom field to which the new enum option will be added. |
| data | object | – | The payload defining the new enum option's properties, such as its name, color, and enabled state. |
No output schema declared.
No examples provided.
create_goal Create Goal ~61
Creates a new goal within a specified workspace or team. Returns the full record of the newly created goal.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The goal object containing the details for the new goal, such as name, owner, due date, and associated workspace or team. |
No output schema declared.
No examples provided.
create_membership Create Membership ~79
Creates a new membership linking a Team or User to a goal, project, portfolio, custom type, or custom field. Returns the full record of the newly created membership.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | The membership details including the resource to join (goal, project, portfolio, custom type, or custom field) and the member to add (Team or User). |
No output schema declared.
No examples provided.
create_organization_export Create Organization Export ~54
Initiates an export request for an entire Asana organization. Asana processes and completes the export asynchronously after the request is submitted.
| Name | Type | Req | Description |
|---|---|---|---|
| organization | string | – | The globally unique identifier of the workspace or organization to export. |
No output schema declared.
No examples provided.
create_portfolio Create Portfolio ~79
Creates a new portfolio in a specified workspace with a given name. Note that portfolios created via the API will not include default UI state (such as the 'Priority' custom field) to allow integrations to define their own initial configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Request body containing the portfolio details, including the name and workspace to create the portfolio in. |
No output schema declared.
No examples provided.
create_project Create Project ~66
Creates a new project within a specified workspace or organization, optionally associating it with a team. Returns the full record of the newly created project.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The request body containing project details such as name, workspace, team, and privacy settings required to create the project. |
No output schema declared.
No examples provided.
create_project_brief Create Project Brief ~91
Creates a new project brief for the specified project, returning the full record of the newly created brief. Project briefs provide a structured summary of project goals, context, and key information.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The request body containing the fields and values for the new project brief to be created. |
| project_gid | string | yes | The globally unique identifier of the project for which the brief will be created. |
No output schema declared.
No examples provided.
create_project_from_template Create Project from Template ~274
Instantiates a new project from an existing project template, returning an asynchronous job that handles the creation process. Supports mapping template date variables and roles to specific calendar dates and users at instantiation time.
| Name | Type | Req | Description |
|---|---|---|---|
| is_strict | boolean | – | Controls how unfulfilled date variables are handled. When true, the request fails with an error if any date variable is missing a value; when false, missing date variables fall back to a default such… |
| name | string | – | The display name to assign to the newly created project. |
| project_template_gid | string | yes | The globally unique identifier of the project template to instantiate. Retrieve this value from the get project template endpoint. |
| requested_dates | array | – | An array of objects mapping each template date variable (identified by its GID from the template's requested_dates array) to a specific calendar date. Required when the project template contains date… |
| requested_roles | array | – | An array of objects mapping each template role to a specific user identifier, used to assign team members to predefined roles defined in the project template. |
| team | string | – | The unique identifier of the team to assign to the new project. Applicable only when the workspace is an organization; defaults to the same team as the source project template if omitted. |
No output schema declared.
No examples provided.
create_project_in_workspace Create Project in Workspace ~91
Creates a new project within the specified workspace or organization. If the workspace is an organization, a team must also be provided to share the project with.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The project details to use when creating the new project, such as name, team, and other project attributes. |
| workspace_gid | string | yes | The globally unique identifier of the workspace or organization in which to create the project. |
No output schema declared.
No examples provided.
create_project_status Create Project Status ~99
Creates a new status update on a specified project and returns the full record of the newly created status. Note: this endpoint is deprecated; new integrations should use the `/status_updates` route instead.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The request body containing the status update fields, such as title, text, color, and other relevant status details. |
| project_gid | string | yes | The globally unique identifier of the project on which to create the status update. |
No output schema declared.
No examples provided.
create_rate Create Rate ~112
Creates a billing rate for a specific resource (user or placeholder) within a parent project, defining the monetary value charged for that resource's time.
| Name | Type | Req | Description |
|---|---|---|---|
| parent | string | yes | The globally unique ID of the parent project to which this rate will be assigned. |
| rate | number | yes | The monetary value of the rate to assign to the resource, representing the billing amount per unit of time. |
| resource | string | yes | The globally unique ID of the resource (user or placeholder) for whom the rate is being set. |
No output schema declared.
No examples provided.
create_resource_export Create Resource Export ~150
Initiates an asynchronous bulk export of workspace resources (tasks, teams, or messages) in gzip-compressed JSON Lines format. Export progress can be monitored via the jobs endpoint, and the resulting file is accessible for 30 days after completion.
| Name | Type | Req | Description |
|---|---|---|---|
| export_request_parameters | array | – | An array of export request parameter objects, where each object specifies a resource GID and its associated export options (such as filters and fields). Providing multiple entries for the same resour… |
| workspace | string | – | The GID of the workspace whose resources will be exported. Only one in-progress export is permitted per workspace at a time. |
No output schema declared.
No examples provided.
create_section Create Section ~152
Creates a new section within a specified project to help organize tasks. Returns the full record of the newly created section.
| Name | Type | Req | Description |
|---|---|---|---|
| insert_after | string | – | The GID of an existing section in this project after which the new section will be inserted. Mutually exclusive with insert_before; only one may be provided. |
| insert_before | string | – | The GID of an existing section in this project before which the new section will be inserted. Mutually exclusive with insert_after; only one may be provided. |
| name | string | – | The display name for the new section. Must be a non-empty string. |
| project_gid | string | yes | The unique identifier of the project in which the new section will be created. |
No output schema declared.
No examples provided.
create_status_update Create Status Update ~82
Creates a new status update on a specified object, such as a project or task. Returns the full record of the newly created status update.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The payload containing the status update details to be created on the target object. |
| limit | integer | – | The number of results to return per page, must be between 1 and 100. |
No output schema declared.
No examples provided.
create_subtask Create Subtask ~87
Creates a new subtask under the specified parent task and returns the full record of the newly created subtask.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The subtask details to create, including fields such as name, assignee, due date, and notes. |
| task_gid | string | yes | The unique identifier (GID) of the parent task to which the new subtask will be added. |
No output schema declared.
No examples provided.
create_tag Create Tag ~79
Creates a new tag within a specified workspace or organization, returning the full record of the newly created tag. Requires the tags:write scope, and the tag's workspace association is permanent once set.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The request body containing the tag details, including the required workspace or organization identifier and any additional tag properties such as name and color. |
No output schema declared.
No examples provided.
create_tag_in_workspace Create Tag in Workspace ~81
Creates a new tag within a specified workspace or organization. Returns the full record of the newly created tag.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The tag details to create, including properties such as name, color, and any other supported tag fields. |
| workspace_gid | string | yes | The globally unique identifier of the workspace or organization in which to create the tag. |
No output schema declared.
No examples provided.
create_task Create Task ~92
Creates a new task in a specified workspace, project, or as a child of a parent task. Any fields not explicitly provided will be assigned their default values.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The task fields to set on the new task, such as name, workspace, projects, assignee, due date, and other task attributes. A workspace must be determinable either directly or via an associated project… |
No output schema declared.
No examples provided.
create_team Create Team ~49
Creates a new team within the current workspace. Use this to organize members and resources under a named group.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The configuration details for the new team, such as name and settings. |
No output schema declared.
No examples provided.
create_team_project Create Team Project ~72
Creates a new project shared with the specified team. Returns the full record of the newly created project.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The project details and configuration to use when creating the new team project. |
| team_gid | string | yes | The globally unique identifier of the team with which the new project will be shared. |
No output schema declared.
No examples provided.
create_time_entry Create Time Entry ~240
Logs a new time tracking entry on a specified task, recording duration, date, billable status, and optional project attribution. Returns the newly created time tracking entry record.
| Name | Type | Req | Description |
|---|---|---|---|
| attributable_to | string | – | The GID of the project this time entry should be attributed to, allowing time to be associated with a specific project context. |
| billable_status | string | – | The billable classification of this time entry: 'billable' for client-chargeable time, 'nonBillable' for internal time, or 'notApplicable' when billing status is not relevant. |
| description | string | – | A free-text note describing the work performed during this time entry, providing context for the logged time. |
| duration_minutes | integer | – | The amount of time to log for this entry, expressed in whole minutes. Must be greater than 0. |
| entered_on | string | – | The calendar date this time entry is logged against, in ISO 8601 date format (YYYY-MM-DD). Defaults to today if omitted. |
| task_gid | string | yes | The unique identifier (GID) of the task on which the time tracking entry will be created. |
No output schema declared.
No examples provided.
create_timesheet_approval_status Create Timesheet Approval Status ~144
Creates a new timesheet approval status for a specific user's weekly timesheet within a workspace. The week must span exactly Monday through the following Sunday.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | The end date of the timesheet week in ISO 8601 date format; must be the Sunday immediately following the start date. |
| start_date | string | yes | The start date of the timesheet week in ISO 8601 date format; must be a Monday. |
| user | string | yes | The globally unique identifier of the user whose timesheet approval status is being created. |
| workspace | string | yes | The globally unique identifier of the workspace in which the timesheet exists. |
No output schema declared.
No examples provided.
delete_allocation Delete Allocation ~46
Permanently deletes an existing allocation by its unique identifier. Returns an empty data record upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_gid | string | yes | The globally unique identifier of the allocation to delete. |
No output schema declared.
No examples provided.
delete_attachment Delete Attachment ~49
Permanently deletes a specific attachment by its unique identifier. Returns an empty data record upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_gid | string | yes | The globally unique identifier (GID) of the attachment to delete. |
No output schema declared.
No examples provided.
delete_budget Delete Budget ~45
Permanently deletes an existing budget by its unique identifier. Returns an empty data record upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_gid | string | yes | The globally unique identifier of the budget to delete. |
No output schema declared.
No examples provided.
delete_custom_field Delete Custom Field ~58
Permanently deletes an existing custom field by its unique identifier. Note that locked custom fields can only be deleted by the user who originally locked the field.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_field_gid | string | yes | The globally unique identifier of the custom field to delete. |
No output schema declared.
No examples provided.
delete_goal Delete Goal ~45
Permanently deletes an existing goal by its unique identifier. Returns an empty data record upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| goal_gid | string | yes | The globally unique identifier of the goal to delete. |
No output schema declared.
No examples provided.
delete_membership Delete Membership ~56
Permanently removes an existing membership from a goal, project, portfolio, custom type, or custom field. Returns an empty data record upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| membership_gid | string | yes | The globally unique identifier of the membership to delete. |
No output schema declared.
No examples provided.
What is the com.mcparmory/asana MCP server?
com.mcparmory/asana is an MCP server listed in the public MCP registry as com.mcparmory/asana. Manage tasks, projects, portfolios, and team workflows. This page covers its container image (ghcr.io/mcparmory/asana:1.0.5).
Is the com.mcparmory/asana MCP server safe to use?
com.mcparmory/asana scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/asana MCP server expose?
com.mcparmory/asana exposes 220 tools: list_access_requests, request_access, approve_access_request, reject_access_request, get_allocation, and 215 more. Their descriptions and schemas cost roughly 25,088 tokens of context every time the server is loaded.
Is the com.mcparmory/asana MCP server still maintained?
com.mcparmory/asana is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.