Skip to main content
Glama
pipeworx-io

mcp-asana

by pipeworx-io
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

mcp-asana

Asana MCP — wraps the Asana REST API (OAuth)

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

asana_list_workspaces

Get all accessible Asana workspaces. Returns workspace names and IDs needed to list projects and tasks.

asana_list_tasks

List tasks in a project. Returns task ID, name, completion status, assignee, and due date. Requires project ID.

asana_get_task

Get full task details including name, description, assignee, projects, tags, subtasks, and status. Requires task ID.

asana_create_task

Create a new task in a project. Returns task ID, name, and permalink. Requires project ID and task name.

asana_list_projects

List all projects in a workspace. Returns project ID, name, and archived status. Requires workspace ID.

asana_search_tasks

Search tasks across a workspace by keyword. Returns matching tasks with ID, name, completion status, and assignee. Requires workspace ID.

Related MCP server: Asana MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "asana": {
      "url": "https://gateway.pipeworx.io/asana/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/asana/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Asana data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

This server cannot be installed

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-asana'

If you have feedback or need assistance with the MCP directory API, please join our Discord server