The Todo MCP Server provides an autonomous task management system that can operate over both stdio and HTTP transports. When using the stdio transport, you interact with the server through standard input and receive responses on standard output, enabling seamless integration with local tooling and GUI wrappers. The server includes a built-in task management workflow with an autonomous AI agent capable of generating, managing, and executing task lists with persistent storage in SQLite. It also exposes a Streamable HTTP API so clients can subscribe to real-time updates via Server-Sent Events (SSE) and issue commands over REST.

To start using the stdio transport directly, you can invoke the MCP via npx, which points to the public repository: npx github:stilllovee/todo-mcp-server. If you clone the repository locally, you can run the server with Node.js by pointing to the folder containing the server code, e.g. node PATH_TO_YOUR_FOLDER. For HTTP (Streamable) transport, you can start the HTTP server (port 8123 by default) and access the MCP at http://localhost:8123/mcp. You can also configure Copilot-style setups to target either stdio or HTTP endpoints by providing the appropriate type (stdio or http) and the associated command and arguments in your MCP configuration. The server exposes two primary tools for task management: add (to create tasks) and next (to fetch the next pending task).

Prerequisites:

• Node.js and npm installed on your machine (Node >= 14 recommended)
• Git (for cloning the repository)

Option A: Use npx (no local install required)

1. Ensure you have Node and npm installed.
2. Run a project-agnostic command to start the server via npx: npx github:stilllovee/todo-mcp-server

Option B: Clone the repository and run locally

1. Clone the repository: git clone https://github.com/stilllovee/todo-mcp-server.git
2. Navigate into the project folder: cd todo-mcp-server
3. Install dependencies (if applicable): npm install
4. Start the server (stdio or http depending on your setup):
   • For stdio via npm script (if defined): npm run start:stdio
   • Or run directly with node from the project folder (stdio): node path/to/server.js
5. For HTTP transport, start the HTTP server (defaults to port 8123): npm run start:http

   or with a specific port:

   node http-server.js --port=3000

Notes:

• If you are using the npx approach, you do not need to install anything locally beyond npm/npx support.
• If you clone the repo, ensure all dependencies are installed and the path to the server file is correct in your start command.

Tips and considerations:

• The server persists all tasks in SQLite, providing session isolation so each session maintains its own task list.
• When using the HTTP transport, the API supports Server-Sent Events for real-time task updates. Ensure your client handles SSE streams appropriately.
• Available task tools include add (to create a new task) and next (to retrieve the next pending task). You can compose higher-level workflows by chaining these tools in an autonomous agent loop.
• If you run into port conflicts, you can override the HTTP port when starting the server (see the command examples in the README).