DoLoop

com.getdoloopPublished by getdoloop.comOfficial publisherv0.6.2Updated Oct 24, 2026

Recurring tasks in loops. Your assistant reads today's tasks, checks or skips them, edits loops.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

DoLoop connects an assistant to recurring task loops so it can read today's tasks, check or skip them, and edit loops.

What you can do
  • Read today's tasks from the user's recurring loops
  • Mark tasks as checked or skipped
  • Edit existing loops and their recurring tasks
When to use it
Useful when someone tracks recurring routines in DoLoop and wants an assistant to review the day's tasks, tick them off or skip them, and adjust the loops without opening the app.
Requirements
Remote MCP endpoint at api.getdoloop.com over streamable HTTP. Authentication is required: either MCP OAuth sign-in or an API key sent in the Authorization header as a Bearer token, created under My Profile > API keys at getdoloop.com.
Before you install
The server can change data: it checks off, skips and edits loops, so mistakes affect the user's task history. The API key is a secret sent in the Authorization header and should be kept private and revocable.

Installation

In SourceWeft

  1. Open DoLoop in the dashboard and add it to a workspace.
  2. Connect the required 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.getdoloop%2Fdoloop/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. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.6.2LatestOct 19, 2026
  2. v0.5.0Oct 13, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.