asana-full-mcp
Exposes the full Asana REST API via an MCP server, enabling operations like task management and workspace queries, with configurable safety guardrails.
README
asana-full-mcp
A local MCP server exposing the full Asana REST API — usable directly from Claude Code as a stdio server, or packaged as an MCPB bundle for one-click install into Claude Desktop.
Why
Hosted Asana connectors expose a curated subset of the API, and some operations just aren't reachable through them (attaching custom fields to projects, setting library field values, portfolio/goal plumbing, batch endpoints, …). Working around that meant one-off scripts with a PAT every time the curated tools fell short.
This server takes the opposite approach: one generic pass-through tool covering the entire Asana API surface, plus a few curated convenience tools for the common operations — with the safety guardrails enforced in code, not in prompts, so an over-eager model can't talk its way past them.
Tools
| Tool | What it does |
|---|---|
asana_request |
Call any Asana REST endpoint (GET/POST/PUT/DELETE) with arbitrary query/body — full API coverage |
asana_list_workspaces |
List workspaces/organizations visible to the token |
asana_search_tasks |
Task search with common filters plus an extraQuery escape hatch for any Asana search param |
asana_create_task |
Create a task (name, notes, due date, assignee, projects, custom fields, subtask parent) |
asana_update_task |
Update fields on an existing task |
Guardrails
These are enforced in server code, so a confused or over-eager model cannot talk its way past them:
- DELETE is blocked by default. Any
DELETEviaasana_requestis refused unless the bundle was installed with Allow DELETE requests turned on. The curated tools cannot delete at all. - Optional workspace allowlist. If configured, every non-GET request is checked against a list of allowed workspace GIDs. The server resolves the affected workspace from the request body or target resource; if it cannot be determined, the request is refused (fail closed). Reads are never restricted.
Use with Claude Code (stdio)
Build the self-contained server bundle, then register it:
git clone https://github.com/AlexDay3000/asana-full-mcp && cd asana-full-mcp
npm install
npm run build # bundles src/ into server/index.js (no runtime deps needed)
claude mcp add asana-full \
--env ASANA_PAT=your-asana-pat \
--env ASANA_WORKSPACE_ALLOWLIST= \
--env ASANA_ALLOW_DELETE=false \
-- node "$PWD/server/index.js"
Configuration is via environment variables:
| Variable | Required | Notes |
|---|---|---|
ASANA_PAT |
yes | Personal Access Token — create at https://app.asana.com/0/my-apps |
ASANA_WORKSPACE_ALLOWLIST |
no | Comma-separated workspace GIDs writes are restricted to; blank = no restriction |
ASANA_ALLOW_DELETE |
no | true to permit DELETE via asana_request; anything else blocks it |
Use with Claude Desktop (MCPB)
Build the .mcpb bundle (see below) and open it with Claude Desktop.
You'll be prompted for:
| Setting | Required | Notes |
|---|---|---|
| Asana Personal Access Token | yes | Create at https://app.asana.com/0/my-apps |
| Workspace GID allowlist | no | Comma-separated GIDs; blank = writes allowed anywhere the token can reach |
| Allow DELETE requests | no | Default off |
The token is stored by the host's user-config mechanism — it is never baked into the bundle.
Build from source
npm install
npm run pack # esbuild-bundles src/ into server/index.js, then packs the .mcpb
Requires Node 18+ (uses global fetch).
License
This project is not affiliated with or endorsed by Asana, Inc. "Asana" is a trademark of Asana, Inc. Your use of the Asana API through this server is subject to Asana's API terms.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.