Taskboard Port

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Asana workspaces, projects and tasks via the REST API, as MCP tools.

The publisher's own server: Port

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

Taskboard Port's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Taskboard Port in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

taskboard-port

Asana workspaces, projects and tasks as MCP tools, talking to the Asana REST API. taskboard-port is a clean-room rebuild of the core subset of the Asana MCP surface, under a new name: fresh code written from the public Asana API documentation, no copied branding. The original Asana server is hosted/remote with OAuth; this rebuild is a REST client for the same upstream API using a personal access token, and does not reproduce the hosted OAuth surface.

Tools (core subset, 11)

get_current_user, list_workspaces, list_projects, get_project, create_project, list_tasks, get_task, create_task, update_task, delete_task, search_tasks.

Not in this subset: sections, tags, stories/comments, subtasks, custom fields, portfolios/goals, rules, attachments, teams/users admin, typeahead, events/webhooks.

Notes on shaping: Asana wraps request bodies and responses in a data envelope — create/update calls send {data: {...}} and parsed responses are returned as-is. list_tasks picks its route deterministically (project tasks endpoint, else assignee query, else a capped list) and applies the completed filter client-side, since Asana's list endpoints take no such parameter.

Setup

bash
export ASANA_ACCESS_TOKEN=...

Optionally override the API base with ASANA_API_URL (default https://app.asana.com/api/1.0). Without the token, every tool call fails with an error naming the missing variable.

CLI

bash
npx @reneturcios/taskboard-port get_task '{"task_gid":"12345"}'npx @reneturcios/taskboard-port mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

json
{  "mcpServers": {    "taskboard-port": {      "command": "npx",      "args": ["-y", "@reneturcios/taskboard-port", "mcp"],      "env": { "ASANA_ACCESS_TOKEN": "..." }    }  }}

Docker

bash
docker run -i -e ASANA_ACCESS_TOKEN ghcr.io/cloudcorprecords/taskboard-port

Development

bash
npm installnpm run buildnpm test

License

MIT

Source: README.md at commit acb907d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Port integrations