Read and drive your tasks and loops from your own scripts, integrations and AI assistants.
Using Claude, Cursor or another AI assistant? Set up MCP βSend the key as a bearer token in the Authorization header. This lists your loops:
curl -H "Authorization: Bearer dl_β¦" \
https://api.getdoloop.com/api/v1/loopsRequests and responses are JSON, over HTTPS.
DoLoop's MCP server lets Claude, Cursor or any other MCP client read and manage your tasks and loops for you. It uses the same API keys and shares their limit of 60 requests per minute, and it can do nothing your key cannot already do.
Server URL:
https://api.getdoloop.com/mcpCreate a key as in step 1. With a read-only key the assistant gets 5 tools to look at your tasks and loops; with a read-and-write key it gets all 16, so it can also create, edit, check, abort and delete. Create one key per assistant so you can revoke each one on its own.
Run this in a terminal, with your key in place of dl_β¦:
claude mcp add --transport http doloop https://api.getdoloop.com/mcp \
--header "Authorization: Bearer dl_β¦"Claude Desktop's built-in connectors need a sign-in flow that DoLoop does not offer yet. Until then, connect through the mcp-remote bridge (requires Node.js): add this to claude_desktop_config.json, put your key in place of dl_β¦, then restart Claude Desktop.
{
"mcpServers": {
"doloop": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.getdoloop.com/mcp",
"--header",
"Authorization:${DOLOOP_AUTH}"
],
"env": {
"DOLOOP_AUTH": "Bearer dl_β¦"
}
}
}
}Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), with your key in place of dl_β¦:
{
"mcpServers": {
"doloop": {
"url": "https://api.getdoloop.com/mcp",
"headers": {
"Authorization": "Bearer dl_β¦"
}
}
}
}Lists and reads your tasks and loops. GET requests only.
Everything a read-only key can do, plus creating, editing, checking, aborting and deleting tasks and loops.
Paths are relative to the base URL in the example above.
A key cannot touch your account, your password or your other keys: those stay behind your login.
Errors are JSON, with a stable code in the error field:
401 invalid_api_key β the key is malformed or unknown401 api_key_revoked β the key was revoked401 api_key_expired β the key is past its expiry date403 insufficient_scope β a read-only key tried to change something403 api_key_not_allowed β a key was used on an account or key route429 rate_limited β too many requests: wait for Retry-After