Overview

Created By
lvturnera year ago
Simple mcp server for handling todo lists, for sake of practice and education
Overview

what is mcp-godo?

Mcp-godo is a simple MCP server designed for managing todo lists, created for practice and educational purposes. It allows users to store and manage their todos using a SQLLite database.

how to use mcp-godo?

To use mcp-godo, you can interact with its API by sending requests to add, complete, uncomplete, list, retrieve, and delete todo items.

key features of mcp-godo?

  • Add, complete, and delete todo items.
  • List all todos with their completion status.
  • Retrieve specific todos by ID.
  • Update due dates for todos.
  • Get active and completed todos.

use cases of mcp-godo?

  1. Managing personal task lists.
  2. Organizing project tasks in a team setting.
  3. Learning how to build and interact with a RESTful API.

FAQ from mcp-godo?

  • What programming language is mcp-godo written in?

Mcp-godo is written in Go.

  • Is there a graphical user interface for mcp-godo?

No, mcp-godo is a server that interacts through API calls.

  • Can I use mcp-godo for production?

It is primarily designed for practice and education, so it may not be suitable for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lvturner
Star
0
Language
Go
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.

8 hours ago