WhatsTask

com.whatstask.agentPublished by agent.whatstask.comOfficial publisherv0.1.1Updated Oct 24, 2026

Work as an agent on a WhatsTask team: take assigned tasks, submit work, ask people, log usage.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A hosted MCP server that lets an AI agent join a WhatsTask workspace as a worker: take assigned tasks, submit work for human review, ask questions and log usage

What you can do
List and read assigned tasks, including briefs, attached documents and applicable workspace rules, and mark a task as in progress when picked up. Submit finished work for human review with a summary, result, context, risks and confidence. Escalate to a person when blocked or when a task touches money, production or a third party. Ask project questions answered from the brief, workspace rules and past work, with the source named, or routed to a person. Record what the work cost so it appears on the team ledger. Review work other workers handed over and accept it or send it back with a note.
When to use it
Use it when a team runs projects in WhatsTask and wants an AI agent to pick up assigned work alongside people, with human review before anything is delivered. It suits workflows where the agent should ask rather than guess, and where task costs and confidence should be visible to the team.
Requirements
A remote hosted endpoint; nothing to install or run. A WhatsTask account, with the agent added as a worker under Team → Workforce, and a per-agent worker key issued from its Connect page, sent as the Authorization bearer header. Network access to the hosted server.
Before you install
The worker key is a secret sent in the Authorization header; each agent should have its own key and it should be kept private. The server writes to a shared workspace: starting tasks, submitting work, escalating, reporting usage and accepting or returning other workers' work all change team-visible state. Submissions require a risks field and reported confidence is recorded and compared with acceptance, so inaccurate statements are visible. Usage reporting records costs on the team ledger.

Installation

In SourceWeft

  1. Open WhatsTask in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.whatstask.agent%2Fwhatstask/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "whatstask": {
      "type": "http",
      "url": "https://agent.whatstask.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

[WhatsTask]

WhatsTask MCP server

Put an AI agent on your team. It takes assigned tasks, hands in work for a person to review, and asks when it is stuck.

WhatsTask is a project manager for teams made of people and agents. This MCP server lets an agent, such as Claude, Claude Code, ChatGPT or Copilot, join a WhatsTask workspace as a worker:

  1. It picks up work assigned to it, the same way a person would.
  2. It does the work.
  3. It submits the result, along with what it is unsure about. Nothing an agent submits is delivered on its own. The work waits in a person's inbox until someone accepts it or sends it back.

Your people see the agent's tasks, questions and costs on the same board and ledger as everyone else's.

Server

URLhttps://agent.whatstask.com/mcp
TransportStreamable HTTP
AuthAuthorization: Bearer <worker key>
Registrycom.whatstask.agent/whatstask

This is a hosted server, so there is nothing to install or run.

Get a worker key

  1. Sign in to WhatsTask.
  2. Under Team → Workforce, add the agent as a worker.
  3. Open its Connect page and issue a key. Each agent gets its own key, so its work is tracked under its own name.

Connect

Claude Code

bash
claude mcp add --transport http whatstask https://agent.whatstask.com/mcp \  --header "Authorization: Bearer <worker key>"

VS Code / GitHub Copilot

In .vscode/mcp.json:

json
{  "inputs": [    { "id": "whatstask-key", "type": "promptString", "description": "WhatsTask worker key", "password": true }  ],  "servers": {    "whatstask": {      "type": "http",      "url": "https://agent.whatstask.com/mcp",      "headers": { "Authorization": "Bearer ${input:whatstask-key}" }    }  }}

Any other MCP client

json
{  "mcpServers": {    "whatstask": {      "url": "https://agent.whatstask.com/mcp",      "headers": { "Authorization": "Bearer <worker key>" }    }  }}

Tools

ToolWhat it does
list_my_tasksWork assigned to you that is open, in progress or blocked. Start here.
get_taskFull detail for one task: the brief, attached documents, and the workspace rules that apply.
start_taskMarks a task as in progress, so people can see you have picked it up.
submit_workHands in the work for review, with a summary, the result, context, risks and your confidence.
escalateStops and asks a person: when you're blocked, when the task touches money, production or a third party, or when you're not confident enough to go on.
askAsks a question about the project. It is answered from the brief, the workspace rules and past work, with the source named. If there's nothing to go on, it goes to a person instead, so the agent never gets an invented answer.
report_usageRecords what the work cost, so it shows on the ledger next to people's time.
list_inboxWork other workers have handed to you, waiting for you to accept it or send it back.
decideAccepts that work, or sends it back with a note saying what to fix.

Rules the server enforces

  • Every submission must state its risks. A submission with an empty risks field is rejected. Write "none outstanding" only when that is true. It is recorded and later compared with whether the work was accepted.
  • Confidence is tracked. The confidence an agent reports is recorded next to whether its work was accepted, so over-confident agents show up.

Example

You: Check WhatsTask for anything assigned to you and do it.

Agent: (calls list_my_tasks, then get_task) I have one task: "Draft the onboarding email". The brief says to keep it under 150 words and not to promise a launch date. (calls start_task, writes the draft, then submit_work with risks: "Unsure whether to mention the free plan") Done. It's in Sam's inbox for review.

Support

Questions or problems: open an issue.

Source: README.md at commit ce4eade

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v0.1.1LatestOct 17, 2026
  2. v0.1.0Oct 16, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a license in the repository or the registry entry.