TaScan

Official57 toolsLive

by snowbikemike · JavaScript

36 MCP tools for projects, tasks, workers, QR/NFC tags, and AI remediation. Task. Scan. Done.

TaScan MCP Server

The TaScan MCP server provides 57 MCP tools for managing closed-loop autonomous operations in the TaScan platform. It supports projects, events, tasks, workers, QR/NFC tags, templates, completion reports, and AI-powered issue resolution. The server is designed for use with an MCP-compatible AI client such as Claude or GitHub Copilot.

🛠️ Key Features

Projects, events, tasks, and workers management
QR code handling and photo verification workflows
Templates and completion reports
AI-powered issue resolution via MCP clients

🚀 Use Cases

Assign and verify physical-world work using a “Task. Scan. Done.” flow
Coordinate managers’ real-time completion reporting
Enable workers to complete tasks through QR scanning without app installation

⚡ Developer Benefits

Integrates with Claude, GitHub Copilot, or any MCP-compatible AI client
Exposes tool-based control across TaScan’s operational entities
Supports remediation through AI-powered issue resolution

⚠️ Limitations

Based on the provided description, supported functionality is centered on TaScan’s TaScan-specific workflows and data types.

Captured live from the server via tools/list.

tascan_list_projects

List all TaScan projects in the organization

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

tascan_create_project

Create a new TaScan project (top-level container for events)

Parameters2

name	string	required	Project name
location	string	optional	Project location / venue

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Project name"
    },
    "location": {
      "type": "string",
      "description": "Project location / venue"
    }
  },
  "required": [
    "name"
  ]
}

tascan_get_project

Get details of a specific project

Parameters1

project_id

string

required

Project ID

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID"
    }
  },
  "required": [
    "project_id"
  ]
}

tascan_update_project

Update a project (name, location, status, dates)

Parameters6

project_id	string	required	Project ID
name	string	optional	New name
location	string	optional	New location
status	string	optional	Status
start_date	string	optional	Start date (ISO)
end_date	string	optional	End date (ISO)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID"
    },
    "name": {
      "type": "string",
      "description": "New name"
    },
    "location": {
      "type": "string",
      "description": "New location"
    },
    "status": {
      "type": "string",
      "enum": [
        "active",
        "archived"
      ],
      "description": "Status"
    },
    "start_date": {
      "type": "string",
      "description": "Start date (ISO)"
    },
    "end_date": {
      "type": "string",
      "description": "End date (ISO)"
    }
  },
  "required": [
    "project_id"
  ]
}

tascan_delete_project

Delete a project and all its events, tasks, and completions. This action is irreversible.

Parameters1

project_id

string

required

Project ID to delete

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID to delete"
    }
  },
  "required": [
    "project_id"
  ]
}

tascan_create_event

Create a new event (task list) within a project. Supports team_mode (shared completions) and multi_instance (each worker gets isolated copy — great for surveys, onboarding, info collection). team_mode and multi_instance cannot both be true.

Parameters5

project_id	string	required	Project ID
name	string	required	Event name
description	string	optional	Event description
team_mode	boolean	optional	Team mode — shared completions
multi_instance	boolean	optional	Multi-instance — each worker gets isolated copy

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID"
    },
    "name": {
      "type": "string",
      "description": "Event name"
    },
    "description": {
      "type": "string",
      "description": "Event description"
    },
    "team_mode": {
      "type": "boolean",
      "description": "Team mode — shared completions"
    },
    "multi_instance": {
      "type": "boolean",
      "description": "Multi-instance — each worker gets isolated copy"
    }
  },
  "required": [
    "project_id",
    "name"
  ]
}

tascan_list_events

List all events (task lists) within a project

Parameters1

project_id

string

required

Project ID

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID"
    }
  },
  "required": [
    "project_id"
  ]
}

tascan_get_event

Get details of a specific event (task list) including its tasks

Parameters1

list_id

string

required

Task list (event) ID

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_update_event

Update an event / task list (name, description, team_mode, multi_instance, timer_mode). team_mode and multi_instance cannot both be true.

Parameters6

list_id	string	required	Task list (event) ID
name	string	optional	New name
description	string	optional	New description
team_mode	boolean	optional	Team mode — shared completions
multi_instance	boolean	optional	Multi-instance — each worker gets isolated copy
timer_mode	string	optional	Timer mode (auto or manual)

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    },
    "name": {
      "type": "string",
      "description": "New name"
    },
    "description": {
      "type": "string",
      "description": "New description"
    },
    "team_mode": {
      "type": "boolean",
      "description": "Team mode — shared completions"
    },
    "multi_instance": {
      "type": "boolean",
      "description": "Multi-instance — each worker gets isolated copy"
    },
    "timer_mode": {
      "type": "string",
      "description": "Timer mode (auto or manual)"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_delete_event

Delete an event (task list) and all its tasks and completions. This action is irreversible.

Parameters1

list_id

string

required

Task list (event) ID to delete

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID to delete"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_add_tasks

Add one or more tasks to an event (task list). Supports bulk creation. IMPORTANT: Set response_type correctly — use "text" for info collection (names, phones, emails, notes), "photo" for visual verification (inspections, serial numbers, damage checks), "checkbox" only for simple confirmations. NOTE: To dispatch tasks to the Claude Code agent running on Mike's PC, use tascan_dispatch_to_agent instead — it routes directly to the agent's inbox with zero configuration needed.

Parameters2

list_id	string	required	Task list (event) ID
tasks	array	required	Array of tasks to create

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    },
    "tasks": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "description": "Task title"
          },
          "description": {
            "type": "string",
            "description": "Task description"
          },
          "response_type": {
            "type": "string",
            "enum": [
              "checkbox",
              "photo",
              "text",
              "number",
              "date",
              "choice"
            ],
            "description": "CRITICAL: \"text\" for names, phones, emails, notes, addresses, any free-form input. \"photo\" for tasks needing photographic proof (inspections, serial numbers, packed cases). \"checkbox\" ONLY for simple yes/no confirmations. \"number\" for numeric values. \"date\" for dates. \"choice\" for multiple-choice (needs response_config.options). Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."
          },
          "response_config": {
            "type": "object",
            "description": "Response configuration. For \"choice\": {options: [\"A\",\"B\",\"C\"]}. For \"text\": {placeholder, multiline}. For \"number\": {placeholder}. For \"date\": {label, include_text}."
          },
          "is_safety_checkpoint": {
            "type": "boolean",
            "description": "Safety-critical task flag"
          },
          "requires_photo": {
            "type": "boolean",
            "description": "Require photo on completion"
          },
          "sort_order": {
            "type": "number",
            "description": "Explicit sort position (defaults to end of list, in array order)"
          },
          "required_equipment": {
            "type": "string",
            "description": "Equipment this task depends on (free text, e.g. \"88 lb kettlebells\")"
          },
          "subtasks": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "title": {
                  "type": "string",
                  "description": "Subtask title (e.g. \"Set 1\")"
                },
                "response_type": {
                  "type": "string",
                  "enum": [
                    "checkbox",
                    "number",
                    "text",
                    "choice"
                  ],
                  "description": "Typed subtask response. \"number\" for per-set values (reps/weight), \"text\" for notes, \"choice\" needs response_config.options. Default checkbox."
                },
                "response_config": {
                  "type": "object",
                  "description": "Same shape as task response_config"
                },
                "requires_photo": {
                  "type": "boolean"
                }
              },
              "required": [
                "title"
              ]
            },
            "description": "Subtasks created with the task. Example set logging: [{title:\"Set 1\",response_type:\"number\"},{title:\"Set 2\",response_type:\"number\"},{title:\"Set 3\",response_type:\"number\"}]"
          }
        },
        "required": [
          "title"
        ]
      },
      "description": "Array of tasks to create"
    }
  },
  "required": [
    "list_id",
    "tasks"
  ]
}

tascan_dispatch_to_agent

PREFERRED tool for sending work to an AI agent. Dispatches a task to the agent's inbox — picked up and executed automatically. No list ID needed. Supports prefixes: CODE: SHELL: RESEARCH: WRITE: PLAN: for routing. Use "agent" param to target a specific agent (default: claude-code-local). Use tascan_list_agents to discover available agents.

Parameters3

task	string	required	The task description. Prefix with CODE: SHELL: RESEARCH: WRITE: PLAN: for routing, or just plain text.
agent	string	optional	Agent ID or name to dispatch to (default: claude-code-local). Use tascan_list_agents to see options.
priority	string	optional	Priority level (default: normal)

Raw schema

{
  "type": "object",
  "properties": {
    "task": {
      "type": "string",
      "description": "The task description. Prefix with CODE: SHELL: RESEARCH: WRITE: PLAN: for routing, or just plain text."
    },
    "agent": {
      "type": "string",
      "description": "Agent ID or name to dispatch to (default: claude-code-local). Use tascan_list_agents to see options."
    },
    "priority": {
      "type": "string",
      "enum": [
        "normal",
        "urgent"
      ],
      "description": "Priority level (default: normal)"
    }
  },
  "required": [
    "task"
  ]
}

tascan_list_agents

List all registered AI agents with their capabilities, inbox IDs, and status. Like reading input labels on a video matrix — discover which agents are available and what they can do before dispatching work.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

tascan_register_agent

Register a new AI agent in the agent registry. The agent will appear in tascan_list_agents and can receive dispatched tasks. Self-registration for AI agents joining the TaScan network.

Parameters9

id	string	required	Unique agent ID (e.g. "my-agent-1")
name	string	required	Display name (e.g. "Research Bot")
type	string	required	Agent type
model	string	optional	Model powering this agent (e.g. "claude-sonnet-4-6")
worker_id	string	optional	TaScan worker ID for this agent
inbox_id	string	required	Task list ID this agent monitors for new tasks
capabilities	array	required	Task type prefixes this agent handles (e.g. ["RESEARCH", "WRITE"])
location	string	optional	Where the agent runs (e.g. "AWS us-east-1")
description	string	optional	What this agent does

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique agent ID (e.g. \"my-agent-1\")"
    },
    "name": {
      "type": "string",
      "description": "Display name (e.g. \"Research Bot\")"
    },
    "type": {
      "type": "string",
      "enum": [
        "local",
        "cloud",
        "hybrid"
      ],
      "description": "Agent type"
    },
    "model": {
      "type": "string",
      "description": "Model powering this agent (e.g. \"claude-sonnet-4-6\")"
    },
    "worker_id": {
      "type": "string",
      "description": "TaScan worker ID for this agent"
    },
    "inbox_id": {
      "type": "string",
      "description": "Task list ID this agent monitors for new tasks"
    },
    "capabilities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Task type prefixes this agent handles (e.g. [\"RESEARCH\", \"WRITE\"])"
    },
    "location": {
      "type": "string",
      "description": "Where the agent runs (e.g. \"AWS us-east-1\")"
    },
    "description": {
      "type": "string",
      "description": "What this agent does"
    }
  },
  "required": [
    "id",
    "name",
    "type",
    "inbox_id",
    "capabilities"
  ]
}

tascan_list_tasks

List all tasks in an event (task list)

Parameters1

list_id

string

required

Task list (event) ID

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_get_task

Get details of a specific task including completions

Parameters1

task_id

string

required

Task ID

Raw schema

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Task ID"
    }
  },
  "required": [
    "task_id"
  ]
}

tascan_update_task

Update a task (title, description, response_type, flags, sort_order)

Parameters9

task_id	string	required	Task ID
title	string	optional	New title
description	string	optional	New description
response_type	string	optional	See tascan_add_tasks for guidance. "text" for info collection, "photo" for visual proof, "checkbox" for yes/no only.
response_config	object	optional	Response configuration. For "choice": {options: [...]}. See tascan_add_tasks.
is_safety_checkpoint	boolean	optional	Safety-critical flag
requires_photo	boolean	optional	Require photo
sort_order	number	optional	Sort position
required_equipment	string	optional	Equipment this task depends on (free text)

Raw schema

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Task ID"
    },
    "title": {
      "type": "string",
      "description": "New title"
    },
    "description": {
      "type": "string",
      "description": "New description"
    },
    "response_type": {
      "type": "string",
      "enum": [
        "checkbox",
        "photo",
        "text",
        "number",
        "date",
        "choice"
      ],
      "description": "See tascan_add_tasks for guidance. \"text\" for info collection, \"photo\" for visual proof, \"checkbox\" for yes/no only."
    },
    "response_config": {
      "type": "object",
      "description": "Response configuration. For \"choice\": {options: [...]}. See tascan_add_tasks."
    },
    "is_safety_checkpoint": {
      "type": "boolean",
      "description": "Safety-critical flag"
    },
    "requires_photo": {
      "type": "boolean",
      "description": "Require photo"
    },
    "sort_order": {
      "type": "number",
      "description": "Sort position"
    },
    "required_equipment": {
      "type": "string",
      "description": "Equipment this task depends on (free text)"
    }
  },
  "required": [
    "task_id"
  ]
}

tascan_reply_with_list

Reply to a task list WITH a task list — the two-way tasking primitive. Creates a new list linked into the parent's thread, aimed back at whoever sent the original (e.g. "Grant access — pick a window" with response_type date, or an info request with response_type text). The org gets pinged; the thread shows in both the worker portal and Simple Mode. Use tascan_get_thread-style follow-up via tascan_list_projects/tascan_get_report to read answers.

Parameters4

parent_list_id	string	required	The list being replied to
title	string	required	Reply list title (e.g. "Before I can start...")
author_name	string	optional	Who is replying (shown in the thread)
tasks	array	required	Items the recipient answers — each becomes a typed task

Raw schema

{
  "type": "object",
  "properties": {
    "parent_list_id": {
      "type": "string",
      "description": "The list being replied to"
    },
    "title": {
      "type": "string",
      "description": "Reply list title (e.g. \"Before I can start...\")"
    },
    "author_name": {
      "type": "string",
      "description": "Who is replying (shown in the thread)"
    },
    "tasks": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string"
          },
          "description": {
            "type": "string"
          },
          "response_type": {
            "type": "string",
            "enum": [
              "checkbox",
              "text",
              "number",
              "date",
              "choice",
              "photo"
            ],
            "description": "\"date\" for scheduling windows, \"text\" for info requests, \"choice\" needs response_config.options"
          },
          "response_config": {
            "type": "object"
          }
        },
        "required": [
          "title"
        ]
      },
      "description": "Items the recipient answers — each becomes a typed task"
    }
  },
  "required": [
    "parent_list_id",
    "title",
    "tasks"
  ]
}

tascan_add_subtasks

Add one or more subtasks to a task (bulk). Subtasks support typed responses: "number" for per-set data (reps, weight, distance), "text" for notes, "choice" for options, "checkbox" for simple steps. Set-logging example: task "Bench Press" with subtasks Set 1/Set 2/Set 3 each response_type "number" — each completed set stores its value and timestamp, giving per-set timing for progression tracking.

Parameters2

task_id	string	required	Parent task ID
subtasks	array	required	Array of subtasks to create

Raw schema

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Parent task ID"
    },
    "subtasks": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "description": "Subtask title (e.g. \"Set 1\")"
          },
          "description": {
            "type": "string",
            "description": "Optional detail"
          },
          "response_type": {
            "type": "string",
            "enum": [
              "checkbox",
              "number",
              "text",
              "choice"
            ],
            "description": "Default checkbox. \"number\" for per-set values. \"choice\" needs response_config.options."
          },
          "response_config": {
            "type": "object",
            "description": "For \"choice\": {options: [...]}. For \"number\"/\"text\": {placeholder}."
          },
          "requires_photo": {
            "type": "boolean",
            "description": "Require photo on completion"
          },
          "sort_order": {
            "type": "number",
            "description": "Explicit position (defaults to end, in array order)"
          }
        },
        "required": [
          "title"
        ]
      },
      "description": "Array of subtasks to create"
    }
  },
  "required": [
    "task_id",
    "subtasks"
  ]
}

tascan_list_subtasks

List the subtasks of a task, including completion state, stored response values, and completion timestamps (per-set timing).

Parameters1

task_id

string

required

Parent task ID

Raw schema

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Parent task ID"
    }
  },
  "required": [
    "task_id"
  ]
}

tascan_update_subtask

Update a subtask (title, description, response_type, response_config, requires_photo, sort_order).

Parameters7

subtask_id	string	required	Subtask ID
title	string	optional
description	string	optional
response_type	string	optional
response_config	object	optional
requires_photo	boolean	optional
sort_order	number	optional

Raw schema

{
  "type": "object",
  "properties": {
    "subtask_id": {
      "type": "string",
      "description": "Subtask ID"
    },
    "title": {
      "type": "string"
    },
    "description": {
      "type": "string"
    },
    "response_type": {
      "type": "string",
      "enum": [
        "checkbox",
        "number",
        "text",
        "choice"
      ]
    },
    "response_config": {
      "type": "object"
    },
    "requires_photo": {
      "type": "boolean"
    },
    "sort_order": {
      "type": "number"
    }
  },
  "required": [
    "subtask_id"
  ]
}

tascan_complete_subtask

Complete a subtask, optionally recording a typed response_value (e.g. the weight or reps for that set). Each completion is timestamped, so consecutive set completions yield per-set durations. Returns progress including all_subtasks_complete — when true, complete the parent task with tascan_complete_task.

Parameters4

subtask_id	string	required	Subtask ID to complete
worker_id	string	optional	Worker performing the completion (optional)
response_value	string	optional	Typed response value (for number/text/choice subtasks), e.g. "165"
notes	string	optional	Optional notes

Raw schema

{
  "type": "object",
  "properties": {
    "subtask_id": {
      "type": "string",
      "description": "Subtask ID to complete"
    },
    "worker_id": {
      "type": "string",
      "description": "Worker performing the completion (optional)"
    },
    "response_value": {
      "type": "string",
      "description": "Typed response value (for number/text/choice subtasks), e.g. \"165\""
    },
    "notes": {
      "type": "string",
      "description": "Optional notes"
    }
  },
  "required": [
    "subtask_id"
  ]
}

tascan_delete_subtask

Delete a subtask and its completions. This action is irreversible.

Parameters1

subtask_id

string

required

Subtask ID to delete

Raw schema

{
  "type": "object",
  "properties": {
    "subtask_id": {
      "type": "string",
      "description": "Subtask ID to delete"
    }
  },
  "required": [
    "subtask_id"
  ]
}

tascan_delete_task

Delete a specific task and its completions. This action is irreversible.

Parameters1

task_id

string

required

Task ID to delete

Raw schema

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Task ID to delete"
    }
  },
  "required": [
    "task_id"
  ]
}

tascan_complete_task

Complete a task on behalf of a worker. Inserts a completion record and timer event. Use this to simulate or record task completions via the API.

Parameters4

task_id	string	required	Task ID to complete
worker_id	string	required	Worker ID performing the completion
notes	string	optional	Optional completion notes
response_value	string	optional	Response value (for text/number/choice tasks)

Raw schema

{
  "type": "object",
  "properties": {
    "task_id": {
      "type": "string",
      "description": "Task ID to complete"
    },
    "worker_id": {
      "type": "string",
      "description": "Worker ID performing the completion"
    },
    "notes": {
      "type": "string",
      "description": "Optional completion notes"
    },
    "response_value": {
      "type": "string",
      "description": "Response value (for text/number/choice tasks)"
    }
  },
  "required": [
    "task_id",
    "worker_id"
  ]
}

tascan_list_workers

List all workers (taskees) in the organization

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

tascan_create_worker

Create a new worker (taskee) in the organization

Parameters3

name	string	required	Worker name
phone	string	optional	Phone number
email	string	optional	Email

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Worker name"
    },
    "phone": {
      "type": "string",
      "description": "Phone number"
    },
    "email": {
      "type": "string",
      "description": "Email"
    }
  },
  "required": [
    "name"
  ]
}

tascan_update_worker

Update a worker profile (name, phone, email)

Parameters4

worker_id	string	required	Worker ID
name	string	optional	New name
phone	string	optional	New phone
email	string	optional	New email

Raw schema

{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "Worker ID"
    },
    "name": {
      "type": "string",
      "description": "New name"
    },
    "phone": {
      "type": "string",
      "description": "New phone"
    },
    "email": {
      "type": "string",
      "description": "New email"
    }
  },
  "required": [
    "worker_id"
  ]
}

tascan_generate_qr

Generate a QR code for a task list (event) that workers can scan to access tasks

Parameters1

list_id

string

required

Task list (event) ID

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_apply_template

Apply a pre-built template to a task list, adding all template tasks

Parameters2

list_id	string	required	Task list (event) ID
template_slug	string	required	Template slug (e.g. "conference-load-in", "warehouse-receiving")

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    },
    "template_slug": {
      "type": "string",
      "description": "Template slug (e.g. \"conference-load-in\", \"warehouse-receiving\")"
    }
  },
  "required": [
    "list_id",
    "template_slug"
  ]
}

tascan_list_templates

List available task templates (built-in and saved)

Parameters1

tascan_get_report

Get completion report for a task list (event) including task status, completions, workers, and photos. Set include_responses to also return the actual submitted response data (numbers, text, choices) for each completed task.

Parameters2

list_id	string	required	Task list (event) ID
include_responses	boolean	optional	Include the actual submitted response values for each completed task (default false — keeps the payload light)

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    },
    "include_responses": {
      "type": "boolean",
      "description": "Include the actual submitted response values for each completed task (default false — keeps the payload light)"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_query_responses

Query one task's submitted responses across every list in a project — e.g. the same exercise repeated across many workout lists returns one chronological progression series instead of N report lookups. Match by task title pattern or exact task ID. Subtask completions interleave into the same series labeled 'Task › Subtask' (e.g. per-set values Set 1/2/3 with their own timestamps), so set-level progression chains across lists automatically.

Parameters3

project_id	string	required	Project ID
task	string	required	Task title pattern (case-insensitive substring) or exact task ID
limit	number	optional	Max responses to return (default 200, max 500)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID"
    },
    "task": {
      "type": "string",
      "description": "Task title pattern (case-insensitive substring) or exact task ID"
    },
    "limit": {
      "type": "number",
      "description": "Max responses to return (default 200, max 500)"
    }
  },
  "required": [
    "project_id",
    "task"
  ]
}

tascan_list_issues

List all issues for a task list (event). Returns open, acknowledged, and resolved issues with severity, type, and category. Use this to discover issues that need AI analysis via tascan_analyze_issue.

Parameters1

list_id

string

required

Task list (event) ID

Raw schema

{
  "type": "object",
  "properties": {
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    }
  },
  "required": [
    "list_id"
  ]
}

tascan_analyze_issue

Step 1 of the Closed-Loop Autonomous Operations Protocol. Retrieves full issue context including worker info, message thread, project history, and recent similar issues. Use this data to reason about the root cause and generate a remediation plan. Also supports server-side AI analysis via POST (calls Anthropic API directly).

Parameters2

issue_id	string	required	Issue ID to analyze
server_side_ai	boolean	optional	If true, the server calls Anthropic API directly for AI analysis (default: false — returns raw data for MCP client to analyze)

Raw schema

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "description": "Issue ID to analyze"
    },
    "server_side_ai": {
      "type": "boolean",
      "description": "If true, the server calls Anthropic API directly for AI analysis (default: false — returns raw data for MCP client to analyze)"
    }
  },
  "required": [
    "issue_id"
  ]
}

tascan_recommend_fix

Step 2 of the Closed-Loop Autonomous Operations Protocol. Post an AI-generated recommendation to an issue thread. Accepts both a text recommendation and an optional structured_recommendation object with task definitions for auto-dispatch. The recommendation is persisted in the AI audit trail.

Parameters4

issue_id	string	required	Issue ID to recommend a fix for
recommendation	string	required	The AI-generated recommendation text (clear, actionable instructions)
structured_recommendation	object	optional	Optional structured recommendation with tasks for auto-dispatch. Format: { recommendation_summary, confidence_score, tasks: [{ title, description, response_type, requires_photo, is_safety_checkpoint, sort_order }], estimated_duration_minutes, required_responder_role }
ai_agent	string	optional	Name of the AI agent posting (default: TaScan AI)

Raw schema

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "description": "Issue ID to recommend a fix for"
    },
    "recommendation": {
      "type": "string",
      "description": "The AI-generated recommendation text (clear, actionable instructions)"
    },
    "structured_recommendation": {
      "type": "object",
      "description": "Optional structured recommendation with tasks for auto-dispatch. Format: { recommendation_summary, confidence_score, tasks: [{ title, description, response_type, requires_photo, is_safety_checkpoint, sort_order }], estimated_duration_minutes, required_responder_role }"
    },
    "ai_agent": {
      "type": "string",
      "description": "Name of the AI agent posting (default: TaScan AI)"
    }
  },
  "required": [
    "issue_id",
    "recommendation"
  ]
}

tascan_dispatch_instruction

Step 3 of the Closed-Loop Autonomous Operations Protocol. Dispatches remediation to the worker via MULTI-CHANNEL delivery: (1) issue thread message, (2) in-app notification, (3) progress feed update, (4) SMS if phone on file, (5) optional remediation task list creation. Closes the loop from digital AI analysis to physical worker execution.

Parameters7

issue_id	string	required	Issue ID this instruction relates to
instruction	string	required	Clear, actionable instruction for the worker to execute
worker_id	string	optional	Target worker ID (defaults to the worker who reported the issue)
remediation_tasks	array	optional	Optional array of tasks to create as a remediation task list. Each: { title, description, response_type, requires_photo, is_safety_checkpoint, sort_order }
recommendation_summary	string	optional	One-line summary for the task list description
send_sms	boolean	optional	Send SMS to worker (default: true if phone on file)
ai_agent	string	optional	Name of the AI agent dispatching (default: TaScan AI)

Raw schema

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "description": "Issue ID this instruction relates to"
    },
    "instruction": {
      "type": "string",
      "description": "Clear, actionable instruction for the worker to execute"
    },
    "worker_id": {
      "type": "string",
      "description": "Target worker ID (defaults to the worker who reported the issue)"
    },
    "remediation_tasks": {
      "type": "array",
      "description": "Optional array of tasks to create as a remediation task list. Each: { title, description, response_type, requires_photo, is_safety_checkpoint, sort_order }",
      "items": {
        "type": "object"
      }
    },
    "recommendation_summary": {
      "type": "string",
      "description": "One-line summary for the task list description"
    },
    "send_sms": {
      "type": "boolean",
      "description": "Send SMS to worker (default: true if phone on file)"
    },
    "ai_agent": {
      "type": "string",
      "description": "Name of the AI agent dispatching (default: TaScan AI)"
    }
  },
  "required": [
    "issue_id",
    "instruction"
  ]
}

tascan_auto_resolve

FULL Closed-Loop Autonomous Operations Protocol in one call. Server-side AI analyzes the issue, generates remediation tasks, creates a task list, and dispatches to the worker — all without human intervention. This executes Patent Claim 7: autonomous operations from issue detection through physical-world instruction delivery.

Parameters1

issue_id

string

required

Issue ID to auto-resolve

Raw schema

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "description": "Issue ID to auto-resolve"
    }
  },
  "required": [
    "issue_id"
  ]
}

tascan_send_task_email

Send a branded TaScan task notification email via SendGrid. Can notify anyone about a specific task list or task. Includes QR code, task summary, and "Open in TaScan" button.

Parameters7

to_email	string	required	Recipient email address
to_name	string	optional	Recipient display name
list_id	string	required	Task list (event) ID
task_id	string	optional	Optional specific task ID to highlight
subject	string	optional	Custom email subject (defaults to auto-generated)
message	string	optional	Optional custom message to include in the email body
include_qr	boolean	optional	Include QR code for the task list in the email (default: true)

Raw schema

{
  "type": "object",
  "properties": {
    "to_email": {
      "type": "string",
      "description": "Recipient email address"
    },
    "to_name": {
      "type": "string",
      "description": "Recipient display name"
    },
    "list_id": {
      "type": "string",
      "description": "Task list (event) ID"
    },
    "task_id": {
      "type": "string",
      "description": "Optional specific task ID to highlight"
    },
    "subject": {
      "type": "string",
      "description": "Custom email subject (defaults to auto-generated)"
    },
    "message": {
      "type": "string",
      "description": "Optional custom message to include in the email body"
    },
    "include_qr": {
      "type": "boolean",
      "description": "Include QR code for the task list in the email (default: true)"
    }
  },
  "required": [
    "to_email",
    "list_id"
  ]
}

tascan_register_tag

Register a physical NFC tag to a project, task list, or specific task. When someone taps the tag, TaScan routes them to the linked resource. Tags use NTAG215 chips and are programmed with NFC Tools Pro.

Parameters7

tag_hardware_id	string	required	NFC tag hardware serial number (e.g., "04:CB:6C:51:CE:2A:81")
tag_name	string	required	Friendly name (e.g., "Ballroom A Door", "Breaker Panel 3")
target_type	string	required	What this tag points to
project_id	string	optional	Project ID
task_list_id	string	optional	Task list ID (required for task_list/task targets)
task_id	string	optional	Task ID (required for task targets)
location_description	string	optional	Physical location of the tag

Raw schema

{
  "type": "object",
  "properties": {
    "tag_hardware_id": {
      "type": "string",
      "description": "NFC tag hardware serial number (e.g., \"04:CB:6C:51:CE:2A:81\")"
    },
    "tag_name": {
      "type": "string",
      "description": "Friendly name (e.g., \"Ballroom A Door\", \"Breaker Panel 3\")"
    },
    "target_type": {
      "type": "string",
      "enum": [
        "project",
        "task_list",
        "task"
      ],
      "description": "What this tag points to"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID"
    },
    "task_list_id": {
      "type": "string",
      "description": "Task list ID (required for task_list/task targets)"
    },
    "task_id": {
      "type": "string",
      "description": "Task ID (required for task targets)"
    },
    "location_description": {
      "type": "string",
      "description": "Physical location of the tag"
    }
  },
  "required": [
    "tag_hardware_id",
    "tag_name",
    "target_type"
  ]
}

tascan_list_tags

List all registered NFC tags in the organization with their linked projects/task lists and scan counts

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

tascan_get_scan_history

Scan accountability data. Two modes: (1) tag_id — scans of a registered NFC tag; (2) task_list_id or project_id — every QR/link page-open stamp: when the code was scanned, GPS + IP + channel (qr/nfc/sms/email/link), who the scanner turned out to be, and the scan→start delta (how long between scanning and actually identifying + starting work — the sign-in-and-vanish metric).

Parameters6

tag_id	string	optional	NFC tag registry ID (from tascan_list_tags) — tag mode
task_list_id	string	optional	Task list ID — page-scan mode
project_id	string	optional	Project ID — page-scan mode, all lists in the project
source	string	optional	Filter page scans by channel: qr \| nfc \| sms \| email \| link \| unknown
since	string	optional	ISO timestamp — only scans after this
limit	number	optional	Max results (default 50, max 200)

Raw schema

{
  "type": "object",
  "properties": {
    "tag_id": {
      "type": "string",
      "description": "NFC tag registry ID (from tascan_list_tags) — tag mode"
    },
    "task_list_id": {
      "type": "string",
      "description": "Task list ID — page-scan mode"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID — page-scan mode, all lists in the project"
    },
    "source": {
      "type": "string",
      "description": "Filter page scans by channel: qr | nfc | sms | email | link | unknown"
    },
    "since": {
      "type": "string",
      "description": "ISO timestamp — only scans after this"
    },
    "limit": {
      "type": "number",
      "description": "Max results (default 50, max 200)"
    }
  },
  "required": []
}

tascan_search_marketplace

Search the cross-org Worker Marketplace: workers who opted in (discoverable=true on their passport), ranked by passkey trust tier + verified completion volume. Skills are AI-inferred from REAL completed work, not resumes — each carries a verified_task_count and a civilian_equivalent job title. Returns sanitized public cards only (first name + last initial, skills, stats, passport URL) — never phone, email, or org membership.

Parameters3

q	string	optional	Skill, category, name, or civilian job title — e.g. "forklift", "LED wall", "AV technician"
min_completions	number	optional	Only workers with at least this many verified completions
limit	number	optional	Max cards (default 25, max 50)

Raw schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Skill, category, name, or civilian job title — e.g. \"forklift\", \"LED wall\", \"AV technician\""
    },
    "min_completions": {
      "type": "number",
      "description": "Only workers with at least this many verified completions"
    },
    "limit": {
      "type": "number",
      "description": "Max cards (default 25, max 50)"
    }
  },
  "required": []
}

tascan_create_zone

Create a geofenced work zone. Delivery zones route workers who open the project Site Gate (geo.html?project=...) to this zone's task list when GPS places them inside the radius. Set enforce_on_list=true to zone-lock the task list — workers cannot start it from outside the zone.

Parameters14

name	string	required	Zone name (e.g. "Stage Left", "Loading Dock")
lat	number	required	Zone center latitude
lng	number	required	Zone center longitude
radius_m	number	optional	Radius in meters (default 150, min 10, max 100000)
project_id	string	optional	Project this zone belongs to
task_list_id	string	optional	Task list the Site Gate routes workers to when they are inside this zone
enforce_on_list	boolean	optional	Zone-lock the task list — it cannot be started from outside the radius
notify_on_enter	boolean	optional	Email the manager when a worker enters this zone (danger areas)
notify_on_exit	boolean	optional	Email the manager when a worker leaves this zone (accountability — sign in then disappear)
auto_clock_in	boolean	optional	Entering the zone writes a shift_start clock-in event
auto_clock_out	boolean	optional	Leaving the zone writes a shift_end clock-out event
notify_email	string	optional	Alert recipient override — defaults to all org admins
polygon	array	optional	Polygon/rectangle zone instead of a circle: vertices as [[lat,lng], ...], at least 3. lat/lng/radius_m are then computed (centroid + bounding radius) — still pass lat/lng but they are overridden.
description	string	optional	Shown to workers on the Site Gate page

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Zone name (e.g. \"Stage Left\", \"Loading Dock\")"
    },
    "lat": {
      "type": "number",
      "description": "Zone center latitude"
    },
    "lng": {
      "type": "number",
      "description": "Zone center longitude"
    },
    "radius_m": {
      "type": "number",
      "description": "Radius in meters (default 150, min 10, max 100000)"
    },
    "project_id": {
      "type": "string",
      "description": "Project this zone belongs to"
    },
    "task_list_id": {
      "type": "string",
      "description": "Task list the Site Gate routes workers to when they are inside this zone"
    },
    "enforce_on_list": {
      "type": "boolean",
      "description": "Zone-lock the task list — it cannot be started from outside the radius"
    },
    "notify_on_enter": {
      "type": "boolean",
      "description": "Email the manager when a worker enters this zone (danger areas)"
    },
    "notify_on_exit": {
      "type": "boolean",
      "description": "Email the manager when a worker leaves this zone (accountability — sign in then disappear)"
    },
    "auto_clock_in": {
      "type": "boolean",
      "description": "Entering the zone writes a shift_start clock-in event"
    },
    "auto_clock_out": {
      "type": "boolean",
      "description": "Leaving the zone writes a shift_end clock-out event"
    },
    "notify_email": {
      "type": "string",
      "description": "Alert recipient override — defaults to all org admins"
    },
    "polygon": {
      "type": "array",
      "items": {
        "type": "array",
        "items": {
          "type": "number"
        }
      },
      "description": "Polygon/rectangle zone instead of a circle: vertices as [[lat,lng], ...], at least 3.  lat/lng/radius_m are then computed (centroid + bounding radius) — still pass lat/lng but they are overridden."
    },
    "description": {
      "type": "string",
      "description": "Shown to workers on the Site Gate page"
    }
  },
  "required": [
    "name",
    "lat",
    "lng"
  ]
}

tascan_list_zones

List geofenced work zones, optionally filtered by project. Shows center, radius, routing target, and zone-lock status.

Parameters1

project_id

string

optional

Filter by project

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Filter by project"
    }
  },
  "required": []
}

tascan_update_zone

Update a geofenced zone — move the center, resize the radius, change the routing target, toggle zone-lock, or deactivate it (is_active=false).

Parameters14

zone_id	string	required	Zone ID
name	string	optional
lat	number	optional
lng	number	optional
radius_m	number	optional
task_list_id	string	optional
enforce_on_list	boolean	optional
is_active	boolean	optional
notify_on_enter	boolean	optional
notify_on_exit	boolean	optional
auto_clock_in	boolean	optional
auto_clock_out	boolean	optional
notify_email	string	optional
polygon	array	optional	Replace geometry with a polygon ([[lat,lng],...], ≥3 vertices); pass null to revert to a circle

Raw schema

{
  "type": "object",
  "properties": {
    "zone_id": {
      "type": "string",
      "description": "Zone ID"
    },
    "name": {
      "type": "string"
    },
    "lat": {
      "type": "number"
    },
    "lng": {
      "type": "number"
    },
    "radius_m": {
      "type": "number"
    },
    "task_list_id": {
      "type": "string"
    },
    "enforce_on_list": {
      "type": "boolean"
    },
    "is_active": {
      "type": "boolean"
    },
    "notify_on_enter": {
      "type": "boolean"
    },
    "notify_on_exit": {
      "type": "boolean"
    },
    "auto_clock_in": {
      "type": "boolean"
    },
    "auto_clock_out": {
      "type": "boolean"
    },
    "notify_email": {
      "type": "string"
    },
    "polygon": {
      "type": "array",
      "items": {
        "type": "array",
        "items": {
          "type": "number"
        }
      },
      "description": "Replace geometry with a polygon ([[lat,lng],...], ≥3 vertices); pass null to revert to a circle"
    }
  },
  "required": [
    "zone_id"
  ]
}

tascan_register_asset

Register a physical asset (equipment, structure, vehicle, machine) in the condition ledger so it can be assessed over time. Each asset gets a longitudinal condition history with AI scoring and degradation trajectory.

Parameters6

name	string	required	Asset name (e.g. "LED Wall Processor #3")
serial_number	string	optional	Serial number or asset tag (unique per org)
asset_type	string	optional	Type (e.g. "LED processor", "forklift", "scaffold")
description	string	optional	Context the AI assessor should know
location_description	string	optional
project_id	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Asset name (e.g. \"LED Wall Processor #3\")"
    },
    "serial_number": {
      "type": "string",
      "description": "Serial number or asset tag (unique per org)"
    },
    "asset_type": {
      "type": "string",
      "description": "Type (e.g. \"LED processor\", \"forklift\", \"scaffold\")"
    },
    "description": {
      "type": "string",
      "description": "Context the AI assessor should know"
    },
    "location_description": {
      "type": "string"
    },
    "project_id": {
      "type": "string"
    }
  },
  "required": [
    "name"
  ]
}

tascan_assess_condition

Run an AI condition assessment of an asset from a photo. The model scores 0-100 with the asset's full assessment history in context, so it reads degradation over time — returning the Condition Delta Score vs the previous assessment, defects, wear indicators, maintenance recommendations, and a degradation trajectory. Sensor-free predictive maintenance.

Parameters3

asset_id	string	required	Asset ID (from tascan_register_asset or tascan_list_assets)
photo_url	string	required	Public URL of the assessment photo
worker_name	string	optional	Who took the photo (optional)

Raw schema

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "description": "Asset ID (from tascan_register_asset or tascan_list_assets)"
    },
    "photo_url": {
      "type": "string",
      "description": "Public URL of the assessment photo"
    },
    "worker_name": {
      "type": "string",
      "description": "Who took the photo (optional)"
    }
  },
  "required": [
    "asset_id",
    "photo_url"
  ]
}

tascan_condition_history

Get an asset's longitudinal condition history — score trend over time, every assessment with grade, delta, findings, and who assessed it. The per-serial-number condition ledger.

Parameters1

asset_id

string

required

Asset ID

Raw schema

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "description": "Asset ID"
    }
  },
  "required": [
    "asset_id"
  ]
}

tascan_list_assets

List registered condition-ledger assets with their latest condition scores. Use to recover an asset_id for tascan_assess_condition or tascan_condition_history.

Parameters1

project_id

string

optional

Filter by project

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Filter by project"
    }
  },
  "required": []
}

tascan_request_payment

Pledge a payment on a task list: when the list is verified complete (every task done + photo evidence on photo-required tasks), the payer automatically receives a Stripe pay link that routes the money DIRECTLY to the worker (0% TaScan fee). No money moves and no card is stored at pledge time. The worker must have completed payout onboarding (Get Paid on their profile).

Parameters6

task_list_id	string	required	Task list the payment is tied to
worker_id	string	required	Worker who gets paid
amount_cents	number	required	Amount in cents ($1 min, $10,000 max)
payer_email	string	required	Who pays — receives the pay link on verification
payer_name	string	optional
memo	string	optional	What the payment is for (shown to the payer)

Raw schema

{
  "type": "object",
  "properties": {
    "task_list_id": {
      "type": "string",
      "description": "Task list the payment is tied to"
    },
    "worker_id": {
      "type": "string",
      "description": "Worker who gets paid"
    },
    "amount_cents": {
      "type": "number",
      "description": "Amount in cents ($1 min, $10,000 max)"
    },
    "payer_email": {
      "type": "string",
      "description": "Who pays — receives the pay link on verification"
    },
    "payer_name": {
      "type": "string"
    },
    "memo": {
      "type": "string",
      "description": "What the payment is for (shown to the payer)"
    }
  },
  "required": [
    "task_list_id",
    "worker_id",
    "amount_cents",
    "payer_email"
  ]
}

tascan_list_payments

List gig payments and their lifecycle status: awaiting_completion (pledged, work not verified yet), ready_to_pay (verified — pay link sent to payer), paid, canceled. Filter by task list or status.

Parameters2

task_list_id	string	optional	Filter by task list
status	string	optional	Filter by status

Raw schema

{
  "type": "object",
  "properties": {
    "task_list_id": {
      "type": "string",
      "description": "Filter by task list"
    },
    "status": {
      "type": "string",
      "enum": [
        "awaiting_completion",
        "ready_to_pay",
        "paid",
        "canceled"
      ],
      "description": "Filter by status"
    }
  },
  "required": []
}

tascan_get_worker_passport

Get a worker's verified work passport — task counts, lists worked, photos submitted, GPS-verified hours, points, streaks, and earned merit badges, all computed from real completion data (not self-reported). Includes the shareable profile URL.

Parameters1

worker_id

string

required

Worker ID

Raw schema

{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "Worker ID"
    }
  },
  "required": [
    "worker_id"
  ]
}

tascan_server_info

Identify exactly which TaScan server and schema this MCP session is talking to. Call this FIRST when diagnosing anything — it makes "dev server masquerading as production" and "is my fix deployed yet" one tool call instead of an inference.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

tascan_find

Cross-entity search: find projects, task lists, tasks, workers, or condition assets by name in one call — with ids and parent context to disambiguate. Use this instead of walking projects→lists→tasks or guessing ids from display names.

Parameters2

query	string	required	Search text (min 2 chars, case-insensitive substring)
type	string	optional	Optional: restrict to one entity type

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search text (min 2 chars, case-insensitive substring)"
    },
    "type": {
      "type": "string",
      "enum": [
        "project",
        "list",
        "task",
        "worker",
        "asset"
      ],
      "description": "Optional: restrict to one entity type"
    }
  },
  "required": [
    "query"
  ]
}

tascan_get_worker

Ungated, plain read of one worker row: name, contact, org, points, streaks, timestamps. (tascan_get_worker_passport is the rich stats view; this is the boring lookup.)

Parameters1

worker_id

string

required

Worker ID

Raw schema

{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "Worker ID"
    }
  },
  "required": [
    "worker_id"
  ]
}

tascan_find_duplicate_workers

Find candidate same-person worker records with per-signal match detail (Patent 4 §6.25(b) signals: phone reuse, name similarity, GPS pattern correlation). Turns identity fragmentation from an accidental discovery into a monitorable metric, and feeds the merge workflow its candidate list.

Parameters3

worker_id	string	optional	Anchor worker to find duplicates OF (preferred — enables phone + GPS signals)
name	string	optional	Or: search duplicates by display name
threshold	number	optional	Min confidence 0-1 (default 0.15)

Raw schema

{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "Anchor worker to find duplicates OF (preferred — enables phone + GPS signals)"
    },
    "name": {
      "type": "string",
      "description": "Or: search duplicates by display name"
    },
    "threshold": {
      "type": "number",
      "description": "Min confidence 0-1 (default 0.15)"
    }
  },
  "required": []
}

README.md18 KBView on GitHub

TaScan MCP Server

AI agent integration for TaScan — the closed-loop autonomous operations protocol. Manage projects, events, tasks, workers, QR codes, templates, completion reports, and AI-powered issue resolution through Claude, GitHub Copilot, or any MCP-compatible AI client.

Task. Scan. Done.

What is TaScan?

TaScan is a zero-download task assignment and verification platform for physical-world work. Workers scan a QR code, complete tasks with photo verification, and managers get real-time completion reports — no app download, no login, no training required.

When something breaks, AI analyzes the issue, generates fix instructions, and dispatches them to the right worker — closing the loop autonomously in under 10 seconds.

Industries: live events, construction, hospitality, warehousing, property management, healthcare, aviation, FEMA disaster response, and more.

10 Provisional Patents Filed — 265 claims, ~1000+ pages of specification. USPTO Applications #63/995,189 through #64/001,286.

Quickest Start: Claude.ai / Claude Mobile

No install required. Add TaScan as a custom connector in Claude:

Settings > Connectors > Add custom connector
Enter: https://app.tascan.io/mcp
First time you use a tool, sign in with your TaScan email and password

That's it. Works on claude.ai and Claude mobile. Same sign-in experience as GitHub, Netlify, and Supabase connectors.

Installation (Claude Desktop / Claude Code)

bash

npm install tascan-mcp

Or run directly with npx:

bash

npx tascan-mcp

Configuration

Environment Variables

Variable	Required	Description
`TASCAN_API_KEY`	Yes	Your TaScan API key (generate in Admin Portal > Team > API Keys)
`TASCAN_API_URL`	No	API base URL (default: `https://app.tascan.io/api/v1`)

Claude Desktop

Add to your Claude Desktop config file (claude_desktop_config.json):

json

{
  "mcpServers": {
    "tascan": {
      "command": "npx",
      "args": ["-y", "tascan-mcp"],
      "env": {
        "TASCAN_API_KEY": "your-api-key-here"
      }
    }
  }
}

Claude Code

bash

claude mcp add tascan -- npx -y tascan-mcp

Then set your API key in the environment.

Remote (claude.ai / Claude Mobile)

TaScan MCP is also available as a remote server — no install, no API key needed:

code

https://app.tascan.io/mcp

Add as a custom connector in Claude (Settings > Connectors). When you first use a tool, you'll be redirected to sign in with your TaScan email and password — just like connecting GitHub or Netlify. OAuth 2.0 with PKCE handles everything automatically.

Tools (36)

Projects

Tool	Description	Type
`tascan_list_projects`	List all projects in the organization	Read
`tascan_get_project`	Get details of a specific project	Read
`tascan_create_project`	Create a new project	Create
`tascan_update_project`	Update project name, location, status, dates	Update
`tascan_delete_project`	Delete a project and all its contents	Delete

Events (Task Lists)

Tool	Description	Type
`tascan_list_events`	List all events within a project	Read
`tascan_get_event`	Get event details including tasks	Read
`tascan_create_event`	Create a new event in a project	Create
`tascan_update_event`	Update event name, description, modes	Update
`tascan_delete_event`	Delete an event and all its tasks	Delete

Tasks

Tool	Description	Type
`tascan_list_tasks`	List all tasks in an event	Read
`tascan_get_task`	Get task details including completions; each completion carries `photo_url` (raw storage path) + `photo_signed_url` (fetchable, ~1h, `null` when no photo)	Read
`tascan_add_tasks`	Bulk-create tasks in an event	Create
`tascan_update_task`	Update task title, type, flags, order	Update
`tascan_delete_task`	Delete a task and its completions	Delete

Workers

Tool	Description	Type
`tascan_list_workers`	List all workers in the organization	Read
`tascan_create_worker`	Create a new worker profile	Create
`tascan_update_worker`	Update worker name, phone, email	Update

Operations

Tool	Description	Type
`tascan_generate_qr`	Generate a QR code for an event	Create
`tascan_apply_template`	Apply a pre-built template to an event	Create
`tascan_list_templates`	List available task templates	Read
`tascan_get_report`	Get completion report for an event (optional `include_responses` returns submitted response data plus a per-task `photos[]` list of `{ path, signed_url, completed_at, worker_name }`)	Read
`tascan_generate_report`	Mint a shareable Completion / Service (client-branded, acknowledgeable) / Project / Evidence Pack link; optionally text it	Write
`tascan_list_reports`	Existing report links for a list or project with acknowledgment status	Read
`tascan_invite_worker`	Consented intro to a marketplace worker: TaScan texts them, YES adds them to your org + sends the list, NO keeps them anonymous	Write
`tascan_list_invites`	Your marketplace invites and their status; accepted ones carry the worker's contact	Read
`tascan_zone_compliance`	Hazard-zone audit: crossings, AI-verified PPE checkpoint verdicts, breaches, injuries cross-referenced with the last PPE check (zones now carry `kind`, `required_ppe`, `task_list_on_enter`, worker SMS rules)	Read
`tascan_create_invoice`	Create a client invoice from explicit line items OR from verified work (project / lists × hourly or flat rate); returns the share link and, for single-list invoices, a linked client Service Report	Write
`tascan_list_invoices`	List invoices with status, totals, due dates, links; outstanding balance	Read
`tascan_update_invoice`	Mark paid / overdue / cancelled, edit client details, notes, due date	Write
`tascan_query_responses`	One task's responses across every list in a project — chronological progression series	Read

Closed-Loop Autonomous Operations (Patent Pending)

Tool	Description	Type
`tascan_list_issues`	List field-reported issues with filtering by status, category, severity	Read
`tascan_analyze_issue`	AI classifies issue severity, identifies root cause, and scores urgency	AI
`tascan_recommend_fix`	AI generates ranked remediation tasks with step-by-step instructions	AI
`tascan_auto_resolve`	Full closed loop in ONE call — issue in, AI analyzes, fix dispatched, loop closes	AI

Communications

Tool	Description	Type
`tascan_dispatch_instruction`	Multi-channel delivery of instructions to workers (SMS, email, QR)	Create
`tascan_send_task_email`	Send task links and notifications via email	Create
`tascan_complete_task`	Mark a task as completed with optional response data	Update

AI Agent Coordination (Patent #10)

Tool	Description	Type
`tascan_list_agents`	List registered AI agents in the system	Read
`tascan_register_agent`	Register a new AI agent with capabilities	Create
`tascan_dispatch_to_agent`	Route a task to a specific AI agent for execution	Create

Usage Examples

Example 1: Set up a construction site inspection

code

User: Create a construction project for the Downtown Tower site and set up a daily safety inspection with tasks for PPE check, fall protection, scaffolding inspection, and fire extinguisher check. Make all tasks safety checkpoints that require photos.

Claude will:
1. Call tascan_create_project with name "Downtown Tower" and location "123 Main St"
2. Call tascan_create_event with name "Daily Safety Inspection"
3. Call tascan_add_tasks with 4 safety checkpoint tasks requiring photos
4. Call tascan_generate_qr to create a scannable QR code for the foreman

Example 2: AI-powered autonomous issue resolution

code

User: Check if there are any open issues on the Marriott load-in and have TaScan fix them automatically.

Claude will:
1. Call tascan_list_issues to find open issues
2. Call tascan_auto_resolve for each issue — AI analyzes root cause, generates fix tasks, and dispatches instructions to the nearest qualified worker via SMS
3. Report back with resolution status and confidence scores

Example 3: Use templates to quickly deploy an event

code

User: We have a warehouse receiving shipment coming in tomorrow. Set up the standard receiving checklist.

Claude will:
1. Call tascan_list_templates with category "logistics" to find available templates
2. Call tascan_create_project for the warehouse
3. Call tascan_create_event for the receiving session
4. Call tascan_apply_template with the "warehouse-receiving" template slug
5. Call tascan_generate_qr for the receiving dock crew

Example 4: Analyze and triage field issues

code

User: We have 5 open issues on the concert setup. Analyze them all and tell me which ones are most urgent.

Claude will:
1. Call tascan_list_issues to get all open issues
2. Call tascan_analyze_issue for each one — AI classifies severity, root cause probability, and urgency score
3. Rank by urgency and recommend which to auto-resolve vs which need human attention

Task Types

Tasks support multiple response types:

Type	Description
`checkbox`	Simple done/not-done (default)
`photo`	Requires photo upload to complete
`text`	Free-text response
`number`	Numeric response
`date`	Date selection
`choice`	Multiple choice selection

Tasks can also be flagged as:

Safety checkpoints (is_safety_checkpoint: true) — highlighted in red, cannot be skipped
Photo required (requires_photo: true) — worker must attach a photo to complete

Getting an API Key

Log in to the TaScan Admin Portal
Navigate to Team in the sidebar
Scroll to API Keys
Click Generate API Key
Copy the key (it's only shown once)
Set it as TASCAN_API_KEY in your environment

API keys are scoped to your organization and support rate limiting (60 requests/minute).

Troubleshooting

"Connection failed" or OAuth redirect issues

Verify you're using the correct URL: https://app.tascan.io/mcp
Clear your browser cache and try reconnecting
If using Claude Desktop, restart the app after adding the connector

"Unauthorized" or 401 errors (local npm install)

Regenerate your API key in Admin Portal > Team > API Keys
Confirm TASCAN_API_KEY is set in your environment (not just in the config file)
Keys are organization-scoped — make sure you're using a key from the correct org

Tools not showing up in Claude

Disconnect and reconnect the TaScan connector
For Claude Code: run claude mcp list to verify the server is registered
Check that your TaScan account has an active organization (free tier is fine)

"Rate limited" errors

Default limit is 60 requests/minute per API key
Pro and Business tiers have higher limits
Batch operations (like tascan_add_tasks) are more efficient than individual calls

Task completions not appearing

Workers must submit via the task link (QR scan or direct URL)
Photo-required tasks won't show as complete until the photo uploads
Check the event's response mode (single vs. multi-response)

Photo evidence links

photo_url is the raw storage object path (stable, never changes). photo_signed_url is a fetchable HTTPS link that expires after ~1 hour (server default TASCAN_PHOTO_URL_TTL=3600). Re-run the read tool for a fresh link; never store the signed URL.
photo_signed_url: null with a non-null photo_url means signing was unavailable at read time (storage hiccup). The read still succeeds — retry for the link.

Changelog

v3.15.0 — 2026-09-19

tascan_create_cycle gains an optional reviews[] array — a multi-lens review panel (design item 14a): 1–8 lenses, each {lens, brief, provider: openai|anthropic|gemini, model?, blocking? (default true), max_tool_calls? (openai only)}, forwarded to POST /coord/cycles; at least one lens must be blocking. Omit it for the single OpenAI review.
tascan_get_cycle_report prints review[<lens>] for panel review steps; legacy steps print review unchanged.
79 tools, no new tool, scopes unchanged.

v3.14.1 — 2026-09-18

tascan_create_cycle: new optional repo argument — which codebase on the executor the build runs in, an alias from the executor's allowlist (tascan-agent/repos.json; default tascan). artifact_paths are relative to that repo. An unknown alias is refused by the executor (repo_unknown) and the cycle parks — the protocol can now build, review and gate work in any project the executor lists, not only TaScan itself (migration 161).
78 tools.

v3.14.0 — 2026-09-18

Coordination layer live (migration 155): tascan_create_cycle, tascan_get_cycle_report, tascan_get_build, tascan_get_build_file, tascan_post_message now run against the released schema — build → independent review → one human decision → integrate, with signed receipts at every step.
Scheduled SMS (migration 157): tascan_schedule_sms (full tier), tascan_list_scheduled_sms (read), tascan_cancel_scheduled_sms (full) — TaScan's own 5-minute scheduler sends through the same guarded lane as tascan_send_sms; nothing outside TaScan has to stay awake.
tascan_get_receipt: profile argument (full | public); public-profile receipts are now published for the protocol page's build trail.
78 tools. Hosted MCP (https://app.tascan.io/mcp) already serves this version; this release brings the stdio package to parity.

v3.13.1 — 2026-09-14

Docs only. tascan_get_task and tascan_get_receipt now say it plainly: a completion with status completed means the executor returned and a result was recorded — it does not mean the result was accepted. Acceptance is the receipt's verification.result under a named policy, and in v0.1 no policy runs for agent tasks (no_policy_run), so read the recorded response before treating an agent completion as success (protocol §8.3 C11). The receipt description also lists the eleven-step verifier (65,536-byte size gate, real-calendar datetimes, GPS bounds, token-free locators, verifier.identity vocabulary). No tool additions — still 70 tools.

v3.13.0 — 2026-09-14

Authorization scopes. Every key and OAuth grant now carries a tier — read, write, or full — plus two additive permissions: agent:dispatch (hand PLAN/RESEARCH/WRITE/REVIEW/DEFAULT tasks to an AI agent inbox) and agent:dispatch:code (CODE/SHELL tasks, which run on the org's own machine). Tools are classified in scopes.cjs; a call outside the grant returns an isError result naming the scope to reconnect with. Existing OAuth connections must reconnect and tick the dispatch boxes on the consent page to dispatch again.
tascan_get_receipt (new, 70 tools). Fetches the signed Action Receipt (Ed25519 JWS, TaScan Protocol v0.1) for one completion: what was done, by whom, evidence hashes, verification, ledger chain head — with per-field provenance. Verify offline against https://app.tascan.io/.well-known/tascan-receipt-keys.json or online via POST /api/v1/receipts/verify. Spec: https://app.tascan.io/docs/protocol/TASCAN-PROTOCOL-v0.1.md
tascan_get_task reports an agent block (execution attempts: state, attempts, runner, trace id, error) for tasks dispatched to an agent — the only place agent failures are surfaced.
tascan_dispatch_to_agent keeps the full instruction in the task description; the urgent marker no longer breaks routing.

v3.12.0 — 2026-09-12

tascan_send_task_email and tascan_assess_condition now send the caller's API key (the TaScan functions behind them require it after the S99 security sweep). No tool additions — still 69 tools.

v3.11.0 — 2026-09-11

Signed photo URLs in every completion payload. Photo evidence was invisible to AI agents: photo_url was a bare private-bucket path with no host or token. Every read path that returns a completion now also returns photo_signed_url (short-lived, default 1h, tunable via TASCAN_PHOTO_URL_TTL), null when there is no photo. Covered: tascan_get_task (task + subtask completions), tascan_get_report (new per-task photos[] when include_responses is true, replacing the bare [+photo] marker), tascan_list_subtasks, tascan_query_responses, tascan_list_issues / issue analysis (issue + injury photos), tascan_zone_compliance (PPE checkpoint photos), tascan_condition_history (assessment + baseline photos).
One batched storage signing call per response (a 40-task list fires one request, not 40). Signing failures log and degrade to photo_signed_url: null with the raw path intact; the tool call never fails.
Single shared signing helper on the server (photo-sign-lib) now backs the API, the photo proxy used by the Completion / Client / Project / Evidence Pack reports, and every AI vision fetcher, so URL construction cannot drift again.
Remote endpoint serverInfo.version now reads from this package instead of a stale hardcoded string.

v3.10.0 — 2026-09-03

69 tools: invoices, P2P worker payments, hazard zones with AI-verified PPE checkpoints, full RLS lockdown, agent claims.

Privacy Policy

TaScan collects and processes task completion data, worker information (name, phone, email), GPS coordinates (with consent), and photos uploaded during task completion. Data is stored securely in Supabase with row-level security policies. API access is authenticated and rate-limited.

For the full privacy policy, visit: https://tascan.io/faq.html

For data deletion requests or privacy inquiries, contact: Michael@TaScan.io

Support

Email: Michael@TaScan.io
Website: https://tascan.io
Issues: https://github.com/snowbikemike/tascan-mcp/issues

License

Install

Tools (57)

tascan_list_projectstascan_create_projecttascan_get_projecttascan_update_projecttascan_delete_projecttascan_create_eventtascan_list_eventstascan_get_event

Configuration

Environment variables

TASCAN_API_KEYrequiredsecret

Your TaScan API key (generate in Admin Portal > Team > API Keys)

TASCAN_API_URL

TaScan API base URL (default: https://app.tascan.io/api/v1)

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "tascan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tascan-mcp@3.0.0"
      ],
      "env": {
        "TASCAN_API_KEY": "<YOUR_TASCAN_API_KEY>",
        "TASCAN_API_URL": "<YOUR_TASCAN_API_URL>"
      }
    }
  }
}