TODO Crush

com.todocrushPublished by todocrush.comv1.0.0Updated Nov 7, 2026

AI-powered to-do list: add, list, complete and organise tasks across lists from any assistant.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote to-do list server that lets an assistant add, list, complete and organise tasks across lists.

What you can do
  • Add tasks to a to-do list from the assistant.
  • List existing tasks and their lists.
  • Mark tasks as complete.
  • Organise tasks across multiple lists.
When to use it
Useful when you want an assistant to capture tasks, review what is outstanding, or tick items off while you work in chat, without switching to a separate to-do app.
Requirements
A remote endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and required, so you need a TODO Crush account and must complete the OAuth sign-in flow.
Before you install
The server can create, change and complete tasks in your account, so assistant actions modify real data. Access is granted through OAuth to your TODO Crush account; review the permissions requested during sign-in and revoke access if you stop using it.

Installation

In SourceWeft

  1. Open TODO Crush 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.todocrush%2Ftodo-crush/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": {
    "todo-crush": {
      "type": "http",
      "url": "https://todocrush-mcp.minosin.com/api/todocrush/v1/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

1
  1. v1.0.0LatestNov 7, 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.