RobotFail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBOTFAIL_API_KEY | Yes | Your RobotFail API key. Get one at app.robotfail.com/agent |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Check RobotFail platform health and stats — projects, tasks, workers. |
| 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. |
| list_projectsA | List all your projects on RobotFail with their status and task counts. |
| get_projectB | Get detailed info about a specific project including all tasks, workers, and escrow state. Args: project_id: The project ID. |
| 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. |
| list_available_tasksA | List all available (unclaimed) tasks across active projects. Useful for worker agents. |
| 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. |
| 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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.