MCP MCP Server

Task Manager MCP server

Local serverstdio

What is the MCP MCP server?

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Task Manager MCP server.

What you get

This MCP server allows agents to orchestrate task workflows through exploration. It provides structured task management capabilities for agents working on complex multi-step problems:

Setting it up

The server ships on npm as @blizzy/mcp-task-manager, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

  • Inputs — - title (string): A concise title for this task. Must be understandable out of context
  • Behavior — - All tasks start in the todo status
  • Returns — Confirmation including the created task

Configuration and credentials

You will need one environment variable: SINGLE_AGENT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Choosing this one

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Inputs, Behavior, Returns — is a fair guide to whether it matches your workflow. It is maintained by blizzy; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Inputs- title (string): A concise title for this task. Must be understandable out of context
Behavior- All tasks start in the todo status
ReturnsConfirmation including the created task

How to install the MCP MCP server

Or in Claude Desktop configuration:

```json
{
  "mcpServers": {
    "task-manager": {
      "command": "npx",
      "args": ["-y", "@blizzy/mcp-task-manager"],
      "env": {
        "SINGLE_AGENT": "true"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SINGLE_AGENTConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP to Inputs.
  • Use MCP to Behavior.
  • Use MCP to Returns.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Inputs, Behavior, Returns) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.