Mcp Todo

Created By
br-silvanoa year ago
API de gerenciamento de tarefas via WebSocket com execução modular de comandos e suporte a ferramentas, desenvolvida em TypeScript com banco SQLite. Projetada para integração com agentes de inteligência artificial.
Overview

What is MCP Todo?

MCP Todo is a task management API that utilizes WebSocket for modular command execution and supports integration with artificial intelligence agents. It is developed in TypeScript and uses SQLite as its database.

How to use MCP Todo?

To use MCP Todo, follow these steps:

  1. Ensure execution permission on the commit hook (Husky) by running chmod +x .husky/pre-commit.
  2. Start the development server with npm run dev.
  3. Verify that the Git repository is initialized using git rev-parse --is-inside-work-tree.

Key features of MCP Todo?

  • Modular command execution via WebSocket.
  • Integration capabilities with AI agents.
  • Built with TypeScript and SQLite for robust performance.
  • Comprehensive testing suite using Jest.

Use cases of MCP Todo?

  1. Managing tasks in real-time with WebSocket communication.
  2. Integrating with AI agents for automated task management.
  3. Developing modular applications that require task management functionalities.

FAQ from MCP Todo?

  • Is MCP Todo suitable for production use?

Yes, MCP Todo is designed for production environments with robust features and testing.

  • What are the system requirements?

You need Node.js v20 or higher, npm v10 or higher, and Git installed.

  • How can I contribute to MCP Todo?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
br-silvano
Star
0
Language
TypeScript
License
MIT 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)

a day ago