Acme Todo

com.ritzademoPublished by ritzademo.comOfficial publisherv1.0.0Updated Oct 24, 2026

An MCP server for a simple todo list

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server for a simple todo list, letting an assistant read and manage todo items through a hosted endpoint.

What you can do
List all todos and read a single todo by its identifier, including title, completion status and optional due date. Create new todos with a title and completion status. Replace or partially update an existing todo, for example to mark it completed. Delete todos.
When to use it
Useful when you want an assistant to keep a lightweight shared todo list without setting up your own backend, and the hosted endpoint is acceptable for the data involved.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The endpoint is remote and no authentication is declared, so anyone who can reach it may read or change the list; avoid putting sensitive information in todo titles. Creating, updating and deleting todos change stored data.

Installation

In SourceWeft

  1. Open Acme Todo in the dashboard and add it to a workspace.
  2. 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.ritzademo%2Facme-todo/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.

{
  "mcpServers": {
    "acme-todo": {
      "type": "http",
      "url": "https://mcp.ritzademo.com/mcp/ritza-rzx-our91"
    }
  }
}

README

Simple Todo API - Flask Implementation

A Flask server implementation of the Simple Todo API defined in acmetodo.yaml.

Setup

  1. Install dependencies:
bash
pip install -r requirements.txt
  1. Run the server:
bash
python app.py

The server will start on http://localhost:5000

API Endpoints

  • GET /todos - List all todos
  • POST /todos - Create a new todo
  • GET /todos/{id} - Get a specific todo
  • PUT /todos/{id} - Replace a todo
  • PATCH /todos/{id} - Update a todo
  • DELETE /todos/{id} - Delete a todo

Example Usage

bash
# List all todoscurl http://localhost:5000/todos
# Create a new todocurl -X POST http://localhost:5000/todos \  -H "Content-Type: application/json" \  -d '{"title": "Buy groceries", "completed": false}'
# Get a specific todocurl http://localhost:5000/todos/1
# Update a todocurl -X PATCH http://localhost:5000/todos/1 \  -H "Content-Type: application/json" \  -d '{"completed": true}'
# Delete a todocurl -X DELETE http://localhost:5000/todos/1

Data Format

Todos have the following structure:

  • id (integer, read-only) - Unique identifier
  • title (string, required) - Todo title
  • completed (boolean, default: false) - Completion status
  • dueDate (string, optional) - Due date in YYYY-MM-DD format

Source: README.md at commit ac5902c

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.