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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago