Asana MCP Server Extended
A Model Context Protocol (MCP) server that provides comprehensive Asana integration, enabling AI assistants like Claude to interact with Asana workspaces, projects, tasks, goals, portfolios, and more.
README
Asana MCP Server Extended
A Model Context Protocol (MCP) server that provides comprehensive Asana integration, enabling AI assistants like Claude to interact with Asana workspaces, projects, tasks, goals, portfolios, and more.
Features
- 43 MCP Tools: Full coverage of Asana's API with 29 read-only and 14 write/delete tools
- OAuth 2.0 Authentication: Secure PKCE-based OAuth flow with GitHub integration
- HTTP Transport: Streamable HTTP transport for MCP protocol
- Type-Safe: Built with TypeScript for reliability
- Comprehensive Testing: Full test suite with mocked and integration tests
Quick Start
Prerequisites
- Node.js 18+
- Asana Personal Access Token or OAuth credentials
- (Optional) GitHub OAuth credentials for user authentication
Installation
# Clone the repository
git clone <repository-url>
cd asana-mcp-server-extended
# Install dependencies
npm install
# Build the project
npm run build
Configuration
Set the following environment variables:
# Required: Asana API access token
export ASANA_ACCESS_TOKEN="your_asana_personal_access_token"
# Optional: Custom Asana API base URL (defaults to https://app.asana.com/api/1.0)
export ASANA_API_BASE_URL="https://app.asana.com/api/1.0"
# Optional: Server configuration
export PORT=8766
export HOST=0.0.0.0
# Optional: GitHub OAuth (for user authentication)
export GITHUB_OAUTH_CLIENT_ID="your_github_client_id"
export GITHUB_OAUTH_SECRET="your_github_client_secret"
export GITHUB_OAUTH_CALLBACK_URL="https://your-domain.com/auth/github/callback"
# Optional: Pre-shared tokens (comma-separated)
export MCP_ALLOWED_TOKENS="token1,token2,token3"
Running the Server
# Development
npm run dev
# Production
npm run build
node dist/index.js
The server will start on http://0.0.0.0:8766 by default.
Health Check
curl http://localhost:8766/health
Expected response:
{
"status": "ok",
"server": "asana-mcp-server-http"
}
MCP Client Configuration
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"asana": {
"command": "node",
"args": ["/path/to/asana-mcp-server-extended/dist/index.js"],
"env": {
"ASANA_ACCESS_TOKEN": "your_token_here"
}
}
}
}
HTTP Transport
For HTTP-based MCP clients:
{
"mcpServers": {
"asana": {
"url": "https://your-domain.com/mcp",
"headers": {
"Authorization": "Bearer your_mcp_token"
}
}
}
}
Available Tools
Read-Only Tools (29)
Attachments
asana_get_attachment- Get a single attachment by gidasana_get_attachments_for_object- List attachments for a parent resource
Goals
asana_get_goal- Get a single goalasana_get_goals- List goals filtered by workspace/team/portfolio/time periodasana_get_parent_goals_for_goal- Get parent goals for a goal
Portfolios
asana_get_portfolio- Get a single portfolioasana_get_portfolios- List portfolios in a workspaceasana_get_items_for_portfolio- List items in a portfolio
Projects
asana_get_project- Get a single projectasana_get_projects- List projects filtered by workspace/teamasana_get_projects_for_team- List projects for a teamasana_get_projects_for_workspace- List projects in a workspaceasana_get_project_sections- List sections in a projectasana_get_project_status- Get a project status updateasana_get_project_statuses- List status updates for a projectasana_get_project_task_counts- Get task counts for a project
Tasks
asana_get_task- Get a single taskasana_get_tasks- List tasks filtered by workspace/project/assigneeasana_get_stories_for_task- List stories (activity) for a taskasana_search_tasks- Full-text search for tasks in a workspace
Teams & Workspaces
asana_get_team_users- List users in a teamasana_get_teams_for_user- List teams for a userasana_get_teams_for_workspace- List teams in a workspaceasana_get_workspace_users- List users in a workspaceasana_list_workspaces- List accessible workspaces
Time Periods
asana_get_time_period- Get a time periodasana_get_time_periods- List time periods in a workspace
Users
asana_get_user- Get a user by gid
Search
asana_typeahead_search- Typeahead search within a workspace
Write/Delete Tools (14)
Tasks
asana_create_task- Create a new taskasana_update_task- Update task fieldsasana_delete_task- Delete a taskasana_add_task_followers- Add followers to a taskasana_remove_task_followers- Remove followers from a taskasana_set_parent_for_task- Set or clear task parentasana_set_task_dependencies- Add task dependenciesasana_set_task_dependents- Add task dependentsasana_create_task_story- Create a story/comment on a task
Projects
asana_create_project- Create a new projectasana_create_project_status- Create a project status update
Goals
asana_create_goal- Create a new goalasana_update_goal- Update goal fieldsasana_update_goal_metric- Update a goal's metric
API Reference
All tools follow Asana's REST API conventions:
- GIDs: Asana uses numeric gids (globally unique identifiers) as strings
- Data Wrapping: Request bodies are wrapped in
{ data: {...} } - Response Format: Responses follow
{ data: {...}, next_page: {...} }format - Pagination: Use
limit,offset, andnext_pagefor paginated endpoints - Field Selection: Use
opt_fieldsparameter to request specific fields
See Asana API Documentation for detailed endpoint specifications.
Authentication
Personal Access Token (PAT)
The simplest authentication method. Get your token from Asana Developer Console.
export ASANA_ACCESS_TOKEN="your_pat_here"
OAuth 2.0 Flow
The server supports OAuth 2.0 with PKCE for secure client authentication:
- Client Registration: POST to
/oauth/register - Authorization: GET
/oauth/authorize(redirects to GitHub) - Token Exchange: POST to
/oauth/tokenwith authorization code
See tests/pkce-handshake.test.js for a complete OAuth flow example.
Testing
Run All Tests
npm test
Run Specific Test Suites
# Unit tests
node --test tests/tools/task-tools.test.js
# Integration tests
node --test tests/tools/integration.test.js
# Auth tests
node --test tests/auth.test.js
Test Configuration
Set environment variables for testing:
export ASANA_ACCESS_TOKEN="test_token"
export TEST_BASE_URL="http://localhost:9876"
export MCP_TEST_TARGET="local" # or "remote"
Development
Project Structure
asana-mcp-server-extended/
├── src/
│ ├── index.ts # Main server implementation
│ └── auth.ts # Authentication helpers
├── tests/
│ ├── auth.test.js # Authentication tests
│ ├── pkce-handshake.test.js # OAuth PKCE flow tests
│ ├── tools/
│ │ ├── integration.test.js # Integration tests
│ │ └── task-tools.test.js # Unit tests
│ └── helpers/
│ └── test-server.js # Test server utilities
├── docs/
│ └── guidelines/ # Development guidelines
└── dist/ # Compiled output
Building
npm run build
Type Checking
npm run type-check
Deployment
Environment Variables
Ensure all required environment variables are set in your deployment environment.
Docker
FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY dist ./dist
EXPOSE 8766
CMD ["node", "dist/index.js"]
Health Monitoring
Monitor the /health endpoint for server status:
curl https://your-domain.com/health
Troubleshooting
Common Issues
-
"ASANA_ACCESS_TOKEN environment variable is required"
- Ensure the token is set in your environment
- Check token validity in Asana Developer Console
-
"Asana API error (401)"
- Verify your access token is valid
- Check token permissions/scopes
-
"Invalid gid"
- Asana gids are numeric strings (e.g., "1234567890")
- Ensure gids are passed as strings, not numbers
-
OAuth flow fails
- Verify GitHub OAuth credentials are correct
- Check callback URL matches registered redirect URI
Contributing
- Follow the coding guidelines in
docs/guidelines/ - Write tests for new features
- Update documentation
- Ensure all tests pass
License
[Your License Here]
Support
For issues and questions:
- GitHub Issues: [repository-url]/issues
- Asana API Docs: https://developers.asana.com/reference/rest-api-reference
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.
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.
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.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
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.
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.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
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.