asana-admin-mcp
Related Servers
Alternatives to asana-admin-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server for Asana that accesses every workspace using a personal access token, enabling task and project management through integrated tools like list, create, and complete tasks.-
- AlicenseAqualityCmaintenanceA local MCP server for Asana that uses a personal access token to read and manage Asana projects, tasks, sections, and comments via the standard Asana REST API.815 npmMIT
- AlicenseBqualityCmaintenanceMCP server for the Asana API that allows AI agents to read and optionally write to Asana tasks, comments, and custom fields, with tiered access controls and no delete tools.832 npmMIT
- FlicenseAqualityDmaintenanceAn MCP server that uses AI to generate structured Asana project plans from diverse sources like text, PDFs, and meeting transcripts. It enables users to preview, generate, and directly sync detailed task lists, subtasks, and dependencies into Asana.1-
- AlicenseBqualityCmaintenanceA local MCP server that lets you interact with Asana using a personal access token, providing tools to list projects and tasks, search tasks, create and update tasks, and add comments via the Asana REST API.815 npmMIT
- AlicenseNot gradedqualityCmaintenanceHigh-performance MCP server that transforms how AI assistants interact with Asana, enabling complex task hierarchies and batch operations for efficient project management.11 npm3MIT
TDQS
Scored across 23 tools
Each tool targets a distinct resource and action: user info, members, projects, portfolios, custom fields, sections, and search. There is no overlap in purpose, and descriptions clearly differentiate them.
Most tools follow a consistent 'resource_verb' pattern (e.g., portfolio_create, custom_field_attach, section_reorder), but a few use a generic 'asana_' prefix (asana_whoami, asana_find) and 'project_list_sections' mixes resource prefixes, creating minor inconsistency.
With 23 tools, the server is slightly on the higher side but still well-scoped for Asana administration. Each tool serves a clear purpose, and the count is justified by the breadth of admin operations covered.
The tool set covers core admin operations like project/portfolio/folder/section CRUD, custom field management, and member access. However, it lacks delete operations for projects, portfolios, and members, and is missing a general listing tool for projects/portfolios, which are notable gaps for an admin surface.