# Getdoloop Doloop MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.getdoloop%2Fdoloop
Registry id: `mcp-registry/com.getdoloop/doloop`
Status: live (checked 2026-11-22T17:18:44.246Z)

## Verdict

Getdoloop Doloop MCP server answered 99.99% of Glimind's liveness checks over 30 days, better than 39% of MCP servers, with 485 ms median handshake and 2 outages in 90 days. Its agent-readiness grade is A (93/100) across 16 tools, costing an agent about 3,625 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.99% | 39% of MCP servers |
| Median handshake latency | 485 ms | 27% of MCP servers |
| p95 handshake latency | 619 ms | — |
| Checks in 30 days | 2,085 | — |
| Outages, 90 days | 2 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 93/100 (A) | 67% of MCP servers |
| Tools | 16 | — |
| Tool-list size for an agent | ~3,625 tokens | 35% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "getdoloop-doloop-mcp-server": {
      "type": "http",
      "url": "https://api.getdoloop.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http getdoloop-doloop-mcp-server https://api.getdoloop.com/mcp
```

## Tools (16)

- `abort_task`: Skip an armed task: not this time; the loop moves on. The task is unarmed and its abortions count goes up by 1. On a task that is not armed it changes nothing.
- `arm_all`: Run the arming pass the user asked for, in the user's time zone. 1) A scheduled "drop" task still armed from an earlier day is skipped automatically (missed); o
- `check_task`: Mark an armed task as done: it is unarmed and its ticker goes up by 1. On a task that is not armed it changes nothing (compare ticker before and after).
- `create_loop`: Create an empty loop (a queue of tasks). Add tasks with enqueue_task.
- `create_task`: Create a task. A "schedule" task needs exactly one of dow, cron or every_days. To put a task in a loop, create it with task_type "loop", then call enqueue_task.
- `delete_loop`: Delete a loop for good (its tasks are kept). Cannot be undone: confirm with the user first.
- `delete_task`: Delete a task for good, with its history (ticker, abortions). Cannot be undone: confirm with the user first.
- `dequeue_task`: Remove a task from a loop's queue (the task itself is kept).
- `enqueue_task`: Append one of the user's tasks to the end of a loop's queue.
- `get_loop`: Get one loop with its ordered queue of tasks.
- `get_task`: Get one task.
- `list_loops`: List all loops in the user's DoLoop account, each with its ordered queue of tasks and current_task_id.
- `list_tasks`: List all tasks in the user's DoLoop account (every type, armed or not).
- `todays_tasks`: List the tasks that are armed (due) right now: what the user has to do today.
- `update_loop`: Change a loop's fields. Only the fields you pass change; their previous values are overwritten.
- `update_task`: Change a task's fields. Only the fields you pass change; their previous values are overwritten.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
