MCP Todo.txt Integration

Created By
guifelixa year ago
MCP Todo.txt Integration is an MCP server for managing Todo.txt tasks. Add, update, filter, and organize tasks programmatically via the MCP protocol. Features include searching, sorting, metadata, batch operations, and dynamic updates.
Overview

what is MCP Todo.txt Integration?

MCP Todo.txt Integration is a server implementation of the Model Context Protocol (MCP) that allows users to manage Todo.txt tasks programmatically. It enables adding, updating, filtering, and organizing tasks efficiently.

how to use MCP Todo.txt Integration?

To use the MCP Todo.txt Integration, clone the repository, install the dependencies, and start the server. You can then interact with the server using MCP-compliant clients or tools.

key features of MCP Todo.txt Integration?

  • Add, update, and delete tasks with optional metadata.
  • Filter and sort tasks by various criteria.
  • Perform batch operations for task management.
  • Dynamic task management and session handling.

use cases of MCP Todo.txt Integration?

  1. Automating task management for personal projects.
  2. Integrating with other applications to manage tasks programmatically.
  3. Enhancing productivity by organizing tasks based on context and priority.

FAQ from MCP Todo.txt Integration?

  • Can I use MCP Todo.txt Integration with any Todo.txt file?

Yes! You can configure the path to your Todo.txt file.

  • Is there a way to run this project in development mode?

Yes! You can run the project in development mode using the command npm run dev.

  • What dependencies does this project have?

The project depends on @modelcontextprotocol/sdk, jsTodoTxt, and zod.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
guifelix
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago