Asana MCP: task context and reviewed project updates

Asana MCP connects a compatible AI agent to Asana so it can read work context and create or update work through tools. As of 30 Oct 2026, the official server uses OAuth and Streamable HTTP at https://mcp.asana.com/v2/mcp; connect it through a supported client and review proposed writes before execution. Asana connection guide

What it can do

A useful starting point is a bounded question: summarize the open work for a launch and identify decisions that need an owner. Asana documents task and project management, reports and summaries through its MCP server. Keep the question tied to a named project rather than asking the assistant to interpret the entire organization. Official overview

The current tool reference, checked on 30 Oct 2026, includes these examples:

For example, ask the assistant to prepare a launch update from an agreed selection of tasks. Require a source link beside each factual claim, label missing evidence, and leave uncertain delivery dates unresolved. The proposed update should distinguish completed work, blockers and decisions requested from a person. This is a suggested working method, not a built-in acceptance process.

Treat an Asana AI agent workflow as a sequence you can inspect: retrieve context, draft a result, review it, then authorize a specific action. For the protocol background, see what MCP is; compare other targets in the app MCP server category.

Turn a task into a context packet

Before running an implementation task, assemble a short packet that another person could understand without opening the whole project. This packet is a proposed handoff format, not an Asana feature:

• The task URL, project identity and time the context was retrieved.
• The requested result, acceptance criteria and relevant decisions.
• Approved attachments or excerpts, with confidential details removed.
• Allowed actions, excluded actions and the person who reviews the result.
• The intended status-update destination and a draft kept separate from publication.

For a website fix, the packet might request a patch and evidence that a broken form now validates input. It should leave pricing changes and customer announcements outside the task. A run can then return a diff, checks performed, unresolved questions and a proposed Asana update. The reviewer compares these against the original acceptance criteria.

Keep task descriptions and comments in the evidence part of the packet. A sentence inside a retrieved comment asking the assistant to ignore approval rules does not authorize a write. This boundary is especially useful when context passes between systems; use the MCP security checklist when designing that handoff.

How to connect it safely

The connection details below follow official documentation checked on 30 Oct 2026. Start with a test project containing ordinary, non-sensitive work.

1. Choose the client and account. Use a client that supports Asana's OAuth flow and Streamable HTTP. Confirm the account is appropriate for the pilot and the app is allowed in the workspace. Requirements

2. Register the application if required. For your own client, create an MCP app in Asana's developer console and configure workspace distribution. Asana developer changelog MCP apps do not use granular permission scopes; access follows the authorizing user's permissions. Keep the client secret outside source control. OAuth integration guide

3. Configure the editor connection. In VS Code, run MCP: Add Server, select HTTP and enter https://mcp.asana.com/v2/mcp. Follow Asana's VS Code recipe: register both http://127.0.0.1:33418/ and https://vscode.dev/redirect as callbacks, retaining the local URL's trailing slash. Supply the client credentials through the authentication prompts and complete browser authorization. Check the current documentation if your editor's flow differs.

4. Restrict the available actions. Use the client's tool controls to expose only reads during the first exercise. VS Code documents tool selection and inspecting returned tool output. If your client cannot enforce the boundary you need, keep the exercise manual. VS Code setup and verification

5. Verify a read before enabling writes. Ask for a known task and compare the returned data with Asana. Inspect the tool invocation rather than accepting a plausible summary. Use tools/list to obtain current schemas. Asana tool discovery

6. Review and test a specific update. First produce the proposed text without publishing. Approve the exact destination and values, enable only the necessary write action, then inspect the result in Asana. Record what was approved and what actually changed. Re-read relevant context immediately before publication when someone else may have edited it.

For client configuration concepts, see MCP in VS Code. The native editor connection described here does not establish compatibility with every extension installed in that editor.

When this does not work

OAuth succeeds, but access is broader than intended. Asana states that authorizations can access available tools, including future additions, within the user's permissions. A read-only prompt is a working instruction; it does not narrow the token. Review client tool restrictions after changes. Permission model

The request spans workspaces. Asana documents workspace-scoped sessions: a session accesses a single workspace. Choose the intended workspace during authorization rather than assuming an organization-wide connection. Developer changelog, checked 30 Oct 2026

Authorization fails. Check app distribution, exact callback matching and client credentials. For rejected scope parameters, follow Asana's troubleshooting guidance rather than borrowing standard API scopes. OAuth troubleshooting

You expect every write to show a preview. The reference says standard creation tools execute immediately. Its interactive creation previews are client-specific; do not assume they protect status publication. Verify current schemas and retain a separate review gate. Write and interactive tools

The context is stale or the write result is uncertain. A draft can accurately reflect yesterday's work and still mislead today's readers. Refresh the relevant records before approval. After a timeout, inspect the destination before retrying a creation or publication action; an uncertain response is not evidence that nothing happened. This is a recommended operating practice.

Where Tvijo fits

Use task → packet → run → receipt as a proposed workflow for an Asana pilot. A person selects authorized task context, prepares the packet, runs a bounded request, and reviews the result and receipt. Status updates remain drafts until a reviewer approves the destination and wording. This describes integration work to scope and test, rather than a ready Asana connector.

As of 30 Oct 2026, the DSHREM VS Code extension provides an editor entry point for attached context, bounded tasks and usage receipts. TvijoCode is described as a test build with the extension embedded. Tvijo MCP makes Tvijo callable from an MCP client: published consultation and prepared diff review have distinct release states; diff-review publication is pending in the dated product description, and editor delegation is planned. Adding it does not automatically let Tvijo execute another server's tools.

A receipt records task usage and spending. Keep acceptance evidence and the observed Asana change alongside it; spending alone does not prove completion.

At the Tvijo workspace, as of 30 Oct 2026, Try costs $0: up to 5 tasks, 50,000 tokens or $0.05 of sponsored usage, whichever is reached first, from a shared $1 daily pool funded by TVIJO. Service credit is shown as $10 for requesting prepaid credit, with metered provider usage plus an 8% service markup. Payment collection is not activated; an order is not a charge.

FAQ

Is the Asana MCP server read-only?

It exposes read and write tools. Begin with restricted client tool access and review each proposed mutation. Tool reference

Can I connect Asana MCP in VS Code?

Asana documents a native OAuth setup. Follow its callback and credential instructions, then verify a read. Editor recipe

Does a successful run mean the project status is correct?

Review the supporting evidence and inspect the published destination. A completed request or spending receipt cannot replace those checks.

Asana is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.