Task API Server - MCP TypeScript Implementation

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Task API Server?

Task API Server is a Model Context Protocol (MCP) implementation for a Task Management API written in TypeScript, serving as both a reference implementation and a functional task management server.

How to use Task API Server?

To use the Task API Server, clone the repository, install dependencies, set up your environment variables, and run the server in either STDIO mode for CLI applications or HTTP mode for web access.

Key features of Task API Server?

  • Task Management Operations: List, create, update, and delete tasks with extensive validation and error handling.
  • Dual Interface Modes: Supports both STDIO for command-line applications and HTTP+SSE for web clients.
  • MCP Protocol Implementation: Complete implementation with resources for task data structures and tools for operations.
  • Quality Assurance: Comprehensive test client for validation and automatic server shutdown after tests.

Use cases of Task API Server?

  1. Integrating task management into AI applications.
  2. Building web applications that require task management functionalities.
  3. Automating task operations in CLI-based tools.

FAQ from Task API Server?

  • Can I use Task API Server for any task management needs?

Yes! It provides a flexible and robust solution for various task management requirements.

  • Is there a cost associated with using Task API Server?

No! Task API Server is open-source and free to use.

  • What are the prerequisites for running Task API Server?

You need Node.js 16.x or higher and a package manager like npm or pnpm.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
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