Tiny MCP Server

MCP server implementation for Asana integration

Local serverstdio

What is the Tiny MCP server?

Tiny MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server implementation for Asana integration.

What you get

A Model Context Protocol (MCP) server implementation for Asana integration. This package enables AI assistants to interact with Asana through a standardized protocol, allowing them to manage tasks, projects, and other Asana resources.

  • Asana task management through MCP
  • Project and section listing
  • Task comments retrieval
  • Seamless integration with AI assistants

What the assistant can call

Once Tiny is connected, these are the calls the assistant has available:

  • asana_get_projects — List all accessible projects
  • asana_get_sections_by_project — List sections in a project
  • asana_get_task_stories — Get comments on a task
  • asana_get_task — Retrieve details of a specific task
  • asana_get_tasks_by_project — List tasks in a project
  • asana_get_tasks_by_section — List tasks in a section

Configuration and credentials

You will need one environment variable: ASANA_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

tiny-asana-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tiny's toolset — asana_get_projects, asana_get_sections_by_project, asana_get_task_stories and 3 more — is a fair guide to whether it matches your workflow. It is maintained by bnwebdev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tiny mcp server does with a few real requests.

Available tools

ToolWhat it does
asana_get_projectsList all accessible projects
asana_get_sections_by_projectList sections in a project
asana_get_task_storiesGet comments on a task
asana_get_taskRetrieve details of a specific task
asana_get_tasks_by_projectList tasks in a project
asana_get_tasks_by_sectionList tasks in a section

How to install the Tiny MCP server

{
  "mcpServers": {
    "tiny-asana": {
      "command": "npx",
      "args": ["-y", "tiny-asana-mcp-server"],
      "env": {
        "ASANA_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
ASANA_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Tiny to asana get projects.
  • Use Tiny to asana get sections by project.
  • Use Tiny to asana get task stories.

Frequently asked questions

It connects Tiny to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (asana_get_projects, asana_get_sections_by_project, asana_get_task_stories, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Tiny directly.