Todo

io.github.mctx-aiPublished by GitHub account mctx-aiv2.0.3Updated Oct 24, 2026

Personal todo list that persists across sessions and MCP clients. Create, update, complete, reorder,

VerifiedSSEWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant a persistent personal todo list shared across sessions and MCP clients.

What you can do
The server exposes a personal todo list that persists across sessions and MCP clients. According to the registry description, it supports creating, updating, completing, and reordering tasks. No tool list is published, so the exact tool names and parameters are not documented here.
When to use it
Worth adding when you want an assistant to keep track of tasks for you over time and have those tasks stay available between conversations and across different MCP clients.
Requirements
A remote MCP endpoint reached over SSE at the provider's hosted address; no packages, environment variables, or headers are declared. The manifest declares no authentication, so no credentials are described.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to read or change the list; treat the contents as non-private. The assistant can create, update, complete, and reorder items, which changes stored data. No tool list is published, so review the actual tools before relying on it.

Installation

In SourceWeft

  1. Open 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 SSE. 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/io.github.mctx-ai%2Ftodo/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": {
    "todo": {
      "type": "sse",
      "url": "https://todo.mctx.ai/v2.0.3"
    }
  }
}

Tools

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

Version history

1
  1. v2.0.3LatestSep 16, 2026

Score

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

    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.