Taskqueue

Created By
chriscarrollsmitha year ago
Overview

what is Taskqueue?

Taskqueue is a Model Context Protocol (MCP) server designed for AI task management, enabling AI assistants to handle multi-step tasks with user approval checkpoints.

how to use Taskqueue?

To use Taskqueue, configure it in an MCP client like Claude Desktop or Cursor, and run commands through the CLI to manage tasks and projects.

key features of Taskqueue?

  • Multi-step task planning and management
  • User approval checkpoints for task completion
  • Progress tracking and task status management
  • Enhanced command-line interface for task inspection

use cases of Taskqueue?

  1. Managing complex AI-driven projects with multiple tasks
  2. Ensuring user oversight in task completion
  3. Visualizing task details and progress for better project management

FAQ from Taskqueue?

  • Can Taskqueue handle any type of project?

Yes! Taskqueue is flexible and can manage various projects requiring multi-step task handling.

  • Is Taskqueue easy to integrate with existing tools?

Yes! Taskqueue can be easily configured with various MCP clients and tools.

  • How does Taskqueue ensure task integrity?

Taskqueue enforces strict status transition rules and requires user approval for task completion.

Server Config

{
  "mcpServers": {
    "taskqueue": {
      "command": "npx",
      "args": [
        "-y",
        "taskqueue-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
chriscarrollsmith
Star
-
Language
-
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