Thask MCP Server

What the code does

We read the source, 11 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

postinstall: node install.js

const result = spawnSync(binary, process.argv.slice(2), { stdio: 'inherit' });

    path := filepath.Join(s.Dir, eventsFileName)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add thask -- npx -y @thask-org/cli

{
  "mcpServers": {
    "thask": {
      "args": [
        "-y",
        "@thask-org/cli"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.thask]
command = "npx"
args = ["-y", "@thask-org/cli"]

{
  "mcpServers": {
    "thask": {
      "args": [
        "-y",
        "@thask-org/cli"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "thask": {
      "args": [
        "-y",
        "@thask-org/cli"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: THASK_URL (URL of your Thask server (e.g. https://thask.kimgh06.com or http://localhost:7244). Can also be set via `thask config set url <url>`.), THASK_TOKEN (API key for your Thask account. Generate via `thask login` (browser flow, recommended) or in the web UI settings.). The author declared them in the registry entry; get the values from the project itself.