mcp-server-asana
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASANA_ACCESS_TOKEN | Yes | Your personal access token from the Asana developer console |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| asana_list_workspacesB | List all available workspaces in Asana |
| asana_search_projectsA | Search for projects in Asana using name pattern matching |
| asana_search_tasksB | Search tasks in a workspace with advanced filtering options |
| asana_get_taskB | Get detailed information about a specific task |
| asana_create_taskB | Create a new task in a project |
| asana_get_task_storiesB | Get comments and stories for a specific task |
| asana_update_taskC | Update an existing task's details |
| asana_get_projectC | Get detailed information about a specific project |
| asana_get_project_task_countsB | Get the number of tasks in a project |
| asana_get_project_sectionsB | Get sections in a project |
| asana_create_task_storyA | Create a comment or story on a task. Either text or html_text is required. |
| asana_add_task_dependenciesC | Set dependencies for a task |
| asana_add_task_dependentsB | Set dependents for a task (tasks that depend on this task) |
| asana_create_subtaskB | Create a new subtask for an existing task |
| asana_get_multiple_tasks_by_gidA | Get detailed information about multiple tasks by their GIDs (maximum 25 tasks) |
| asana_get_project_statusC | Get a project status update |
| asana_get_project_statusesB | Get all status updates for a project |
| asana_create_project_statusB | Create a new status update for a project |
| asana_delete_project_statusA | Delete a project status update |
| asana_set_parent_for_taskA | Set the parent of a task and position the subtask within the other subtasks of that parent |
| asana_get_tasks_for_tagC | Get tasks for a specific tag |
| asana_get_tags_for_workspaceA | Get tags in a workspace |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| task-summary | Get a summary and status update for a task based on its notes, custom fields and comments |
| task-completeness | Analyze if a task description contains all necessary details for completion |
| create-task | Create a new task with specified details |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools have distinct purposes targeting specific Asana resources like tasks, projects, statuses, or workspaces. However, some overlap exists: 'asana_get_task' and 'asana_get_multiple_tasks_by_gid' both retrieve task details, which could cause confusion, and dependency-related tools ('asana_add_task_dependencies' vs 'asana_add_task_dependents') are conceptually similar. Descriptions help clarify, but minor ambiguity remains.
All tool names follow a consistent 'asana_verb_noun' pattern with snake_case throughout. The verb-noun structure is predictable (e.g., 'asana_create_task', 'asana_get_project', 'asana_update_task'), making it easy to understand each tool's action and target resource without confusion.
With 22 tools, the count is borderline high for an Asana integration, potentially feeling heavy. While Asana's API is feature-rich, this set includes many specific operations (e.g., separate tools for adding dependencies and dependents) that might be consolidated. It's not excessive but leans toward the upper limit of typical scopes.
The tool set covers core CRUD operations for tasks, projects, and statuses, including search, listing, and updates. Minor gaps exist: there's no tool to delete tasks or projects, and workspace management is limited to listing. However, agents can work around these with available tools, and the surface supports key workflows like task creation, dependency management, and project tracking.