Todo MCP Server

Created By
fyimaila year ago
Overview

what is Todo MCP Server?

Todo MCP Server is a simple Model Context Protocol (MCP) server designed for managing todo items using SQLite database storage.

how to use Todo MCP Server?

To use Todo MCP Server, install the dependencies, configure the database location if needed, and build the project. You can then use the available tools to add, list, or remove todo items.

key features of Todo MCP Server?

  • Add new todo items
  • List all todo items
  • Remove todo items by ID

use cases of Todo MCP Server?

  1. Managing personal task lists
  2. Integrating with other applications for task management
  3. Developing custom todo applications using the MCP protocol

FAQ from Todo MCP Server?

  • What database does Todo MCP Server use?

It uses SQLite for data storage.

  • How do I change the database location?

You can modify the DB_LOCATION variable in src/database.ts to set your preferred location.

  • What programming language is used for this project?

The project is built with TypeScript.

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

Recommend Servers

View All
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.

21 hours ago