When creating a project via the Asana MCP, there’s no way to set custom fields (e.g., Priority, Status dropdowns) at creation time. This forces a second manual step in Asana after the fact, breaking the automation flow. Request: expose custom field GID + enum value parameters in the create_project and create_task MCP tools. Thank you!
You’re absolutely right! The current MCP tools don’t yet expose parameters for setting project or task custom fields at creation time. I can definitely see how that breaks the automation flow, especially when teams rely on standardized fields like Priority or Status. I’ve shared this feedback with the team.
If you’re able to, please also consider adding an upvote here so others can find and support the request as well: Product Feedback - Asana Forum
In the meantime, a few workarounds that may help:
- Projects: If your workflow supports creating projects from templates, you can add the custom fields to the template first so they’re automatically included in every new project.
- Tasks: You can create Rules within the template project to automatically assign default values (like Priority or Status) when new tasks are created.
- Asana API: If you have access to the Asana API outside of MCP, you can currently set
custom_fieldson tasks and projects there until MCP supports this functionality directly.
Really appreciate the clear and thoughtful feedback. I’ll keep an eye on this and share updates if anything changes.