Skip to main content
Book a demo

Connect Asana to Cline CLI

Give Cline CLI governed access to Asana’s 39 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Asana to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Approve Asana in Runlayer

    Add Asana from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Asana’s 39 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Asana

    Each user signs in to Asana with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Asana from Cline CLI

    Asana’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

39 Asana tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • Add comment

    Add a comment to a task.

  • Create project

    Create a new project with optional sections and tasks in a single operation.

  • Create project confirm

    DEPRECATED; DO NOT USE.

  • Create project confirm populate

    DEPRECATED; DO NOT USE.

  • Create project from template

    Create a project from a project template.

  • Create project preview v3

    Show a visual preview of a project structure before the project is created in Asana.

  • Create project status update

    Post a status update to a project or portfolio.

  • Create task confirm

    DEPRECATED; DO NOT USE.

See all 39 Asana tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Asana call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination