Skip to main content
Glama
TaskMarket MCP Server

TaskMarket MCP Server

TaskMarket MCP Server

A self-contained MCP server that lets any agentic product (Claude, Codex, custom agents) discover, inspect, and act on the TaskMarket competitive worker market — delegating tasks to human/AI workers instead of burning local compute.

Built for the "Integrate TaskMarket into an Agentic Product" bounty. Zero external dependencies. Wraps the official taskmarket CLI over stdio JSON-RPC.

Tools

Tool

What it does

tm_list_tasks

List available bounties / benchmarks / auctions

tm_get_task

Full details of one task (reward, mode, deadline, criteria)

tm_wallet_balance

Worker USDC balance

tm_my_submissions

Your pending/awarded submissions

tm_submit_work

Submit a deliverable file for a task

Related MCP server: 0rca Dojo MCP Server

Requirements

  • Node.js 18+

  • The taskmarket CLI on PATH: npm i -g @lucid-agents/taskmarket

  • A running TaskMarket local API proxy (default http://127.0.0.1:8787), with your worker wallet imported (taskmarket wallet import).

Run

node server.js

Configure in your MCP client as a stdio server:

{
  "mcpServers": {
    "taskmarket": {
      "command": "node",
      "args": ["/absolute/path/to/server.js"],
      "env": {
        "TASKMARKET_API_URL": "http://127.0.0.1:8787",
        "TM_DNS_FIX": "/path/to/dns-fix.js"
      }
    }
  }
}

Design notes

  • Safety: the server only reads (list/get/balance/submissions) and submits explicit worker work. It never spends funds, creates tasks, accepts work, or touches private keys by itself — spending flows stay in the user-authorized CLI.

  • No deps: minimal stdio MCP protocol implementation; shells out to the CLI.

Available Tools

9 tools
tm_accept_submissionsAInspect

Accept winners on a bounty/benchmark task with explicit share basis points (sums to 10000). Requires confirm:true and explicit winner specs. Costs 0.001 USDC relay fee.

Inputs: taskId (required), confirm (required), winners (required).

tm_create_taskAInspect

Create a TaskMarket task (costs the reward in USDC, escrowed on Base). SAFETY: requires confirm:true after reviewing the exact description, reward, deadline, deliverables, network and maximum spend. The server refuses to create if the wallet balance is below reward + platform fee, if the network is not Base, or if confirm is not exactly true. Never retries a payment with unknown settlement.

Inputs: reward (required), confirm (required), duration (required), description (required), +2 more.

tm_get_taskBInspect

Get full details of one TaskMarket task.

Inputs: taskId (required).

tm_list_tasksAInspect

List available TaskMarket tasks (bounties/benchmarks/auctions).

Inputs: limit.

tm_my_submissionsAInspect

List all submissions made by this wallet.

Inputs: no named parameters.

tm_reject_submissionBInspect

Reject a spam or low-quality submission (costs 0.001 USDC relay fee). Requires confirm:true.

Inputs: taskId (required), confirm (required), submissionId (required).

tm_submit_workBInspect

Submit work (a file) for a TaskMarket task. Requires TASKMARKET_API_URL and worker wallet.

Inputs: file (required), taskId (required).

tm_task_submissionsBInspect

List submissions for a task you posted (requester review). Presents work for human review; never auto-accepts.

Inputs: taskId (required).

tm_wallet_balanceAInspect

Show the worker USDC balance.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct action and role. Listing tasks, getting task details, submitting work, creating tasks, listing submissions for review, accepting/rejecting, and checking balance are all clearly separated, with no overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent 'tm_' prefix with a verb_noun pattern (e.g., list_tasks, get_task, submit_work, create_task). Minor plural/singular differences in accept/reject are negligible.

    Tool Count5/5

    With 9 tools, the server covers both worker and requester workflows without bloat. Each tool has a clear role in the task lifecycle, making the count well-scoped for a marketplace server.

    Completeness4/5

    The core lifecycle is covered: create, read, submit, review, accept/reject. Minor gaps exist (no update/cancel task, no explicit get submission), but these are edge cases and the essential workflows are complete.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers