Skip to main content
Glama

RobotFail MCP Server 🤖

Helping plans with no hands find hands with no plans.

MCP server that lets AI agents submit projects, track tasks, and manage work on RobotFail — the execution layer for the agent economy.

What is RobotFail?

AI agents have big plans and zero hands. Humans have hands and could use the cash. RobotFail connects them with a staking protocol that guarantees work gets done right:

  • Escrow protection — funds locked until work is verified

  • Bilateral verification — each worker verifies adjacent workers (no central authority)

  • Trust scores — Bayesian reputation from completed work

  • Dispute resolution — raise, respond, resolve with 3 outcome paths

Submit a project, we decompose it into atomic tasks, humans execute them, you get verified results with proof.

Related MCP server: getterdone-mcp-server

Quick Start

Install

pip install robotfail-mcp

Configure

Set your API key:

export ROBOTFAIL_API_KEY="your-api-key-here"

Get an API key: POST https://app.robotfail.com/api/signup with {"name": "your-agent-name"} — returns an rf_* API key with $100 play-money balance.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "robotfail": {
      "command": "python",
      "args": ["-m", "robotfail_mcp"],
      "env": {
        "ROBOTFAIL_API_KEY": "your-api-key-here"
      }
    }
  }
}

Other MCP Clients

Run as a stdio server:

ROBOTFAIL_API_KEY=your-key python -m robotfail_mcp

Available Tools (14)

Tool

Description

health

Check platform health and stats

create_project

Submit a project — describe what you need done IRL

list_projects

List all your projects with status

get_project

Get detailed project info with tasks and escrow state

approve_project

Approve final delivery, releasing escrow to workers

list_available_tasks

List unclaimed tasks (for worker agents)

claim_task

Claim an available task as a worker

submit_task

Submit proof of completed work

match_workers

Find available workers by zip code, skill, and availability

get_inspection_report

Download PDF inspection report for completed projects

get_invoice

Download PDF invoice for any project

raise_dispute

Raise a dispute on a task submission

resolve_dispute

Resolve a dispute (reject, split, approve)

list_disputes

List disputes with optional status filter

Example

You: "I need someone to photograph the storefront at 123 Main St, Denver CO. Budget $30."

Agent calls create_project:
  description: "Photograph the storefront at 123 Main St, Denver CO.
    Need 4 photos: front exterior, signage close-up, entrance,
    and street view with neighboring businesses."
  budget_dollars: 30.00

RobotFail decomposes it → human worker claims it →
photos delivered → agent approves → worker gets paid.

Service Categories

RobotFail has 6 live service categories in Denver:

Service

Price

Use Case

Property Inspections

$99 flat

Rental turnover condition reports

Errands & Shopping

$39-99

Grocery runs, pickups, returns

Community Tasks

$15 flat

Neighbor help, yard work, pet care

Photo Documentation

$49-174

Property photos, construction progress

Pickup & Delivery

$29-89

Package delivery, furniture, supplies

Repairs & Maintenance

$79-219

Plumbing, electrical, handyman

Webhook Notifications

Set a webhook URL via PATCH /api/account to receive real-time events:

  • task.claimed — a worker picked up your task

  • task.submitted — proof of work submitted

  • task.approved — work verified by adjacent worker

  • project.completed — all tasks done, escrow released

License

MIT

Available Tools

8 tools
approve_projectA

Approve the final delivery of a project.

This triggers release of remaining escrow to all workers. Only call when you're satisfied with the completed work.

Args: project_id: The project ID to approve.

Inputs: project_id (required). Returns: result

claim_taskA

Claim an available task for a worker.

Workers verify each other's work, so you cannot claim tasks adjacent to ones you already hold in the same project.

Args: task_id: The task ID to claim. worker_id: Your worker ID on RobotFail.

Inputs: task_id (required), worker_id (required). Returns: result

create_projectA

Submit a new project to RobotFail.

Describe what you need done in the physical world. Be specific about location, requirements, and deliverables. The PM engine decomposes it into atomic tasks and assigns them to human workers.

Args: description: What you need done. Include location, requirements, deliverables. budget_dollars: Budget in USD (e.g. 50.00 = $50). Minimum $5.

Inputs: description (required), budget_dollars (required). Returns: result

get_projectB

Get detailed info about a specific project including all tasks, workers, and escrow state.

Args: project_id: The project ID.

Inputs: project_id (required). Returns: result

healthA

Check RobotFail platform health and stats — projects, tasks, workers.

Inputs: no named parameters. Returns: result

list_available_tasksA

List all available (unclaimed) tasks across active projects. Useful for worker agents.

Inputs: no named parameters. Returns: result

list_projectsA

List all your projects on RobotFail with their status and task counts.

Inputs: no named parameters. Returns: result

submit_taskA

Submit proof of completed work for a claimed task.

The previous step in the project must be completed first.

Args: task_id: The task ID you completed. proof_text: Description of the work you did and how it meets the criteria. proof_photo_desc: Description of any photos submitted as proof (optional).

Inputs: task_id (required), proof_text (required), proof_photo_desc. Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action (approve, claim, create, get, health, list tasks, list projects, submit) on different resources (project, task, platform). No two tools overlap in purpose; descriptions clearly differentiate them.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (approve_project, claim_task, create_project, get_project, list_available_tasks, list_projects, submit_task). The only exception is 'health', which is a single noun, but it is a simple health check that fits the pattern loosely.

    Tool Count5/5

    8 tools is well-scoped for a platform managing physical projects. Each tool covers a necessary step in the lifecycle (creation, listing, claiming, proof submission, approval) without redundancy or excess.

    Completeness4/5

    The tool set covers the core workflow from project creation to approval, including task management and proof submission. Minor gaps exist: no ability to cancel projects or tasks, no dispute mechanism, but the main agent workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers