Model Context Protocol (MCP) server for planning and executing tasks.
Model Context Protocol (MCP) server for planning and executing tasks.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| plan_task | Register a new user request and plan its associated tasks (with optional subtasks). |
| get_next_task | |
| mark_task_done | |
| open_task_details | |
| list_requests | |
| add_tasks_to_request | |
| update_task | |
| delete_task | |
| add_subtasks | |
| mark_subtask_done | |
| update_subtask | |
| delete_subtask | |
| export_task_status | Export the current status of all tasks in a request to a file. It's recommended to use absolute paths for more reliable file creation. |
{
"mcpServers": {
"taskflow": {
"command": "npx",
"args": ["-y", "taskflow-mcp"],
"env": {
"TASK_MANAGER_FILE_PATH": "your-value",
"TASK_MANAGER_BASE_DIR": "your-value",
"ARCHIVE_FILE_PATH": "your-value",
"ARCHIVE_MODE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TASK_MANAGER_FILE_PATH | Filesystem location the server is allowed to use. | Optional |
| TASK_MANAGER_BASE_DIR | Filesystem location the server is allowed to use. | Optional |
| ARCHIVE_FILE_PATH | Filesystem location the server is allowed to use. | Optional |
| ARCHIVE_MODE | Configuration value read at startup. | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Manage Proxmox hypervisors through a Model Context Protocol server, providing a clean interface for nodes, VMs, and containers.