TaScan

Server Details

Universal task protocol — manage projects, tasks, workers, QR codes, and reports.

Status: Healthy
Last Tested: 2026-03-26 16:30
Transport: Streamable HTTP
URL
Repository: snowbikemike/tascan-mcp
GitHub Stars: 0

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

32 tools

tascan_add_tasksInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`tasks`	Yes	Array of tasks to create
`list_id`	Yes	Task list (event) ID

tascan_analyze_issueInspect

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).

ParametersJSON Schema

Name	Required	Description	Default
`issue_id`	Yes	Issue ID to analyze
`server_side_ai`	No	If true, the server calls Anthropic API directly for AI analysis (default: false — returns raw data for MCP client to analyze)

tascan_apply_templateInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID
`template_slug`	Yes	Template slug (e.g. "conference-load-in", "warehouse-receiving")

tascan_auto_resolveInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`issue_id`	Yes	Issue ID to auto-resolve

tascan_complete_taskInspect

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.

ParametersJSON Schema

Name	Required	Description
`notes`	No	Optional completion notes
`task_id`	Yes	Task ID to complete
`worker_id`	Yes	Worker ID performing the completion
`response_value`	No	Response value (for text/number/choice tasks)

tascan_create_eventInspect

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.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Event name
`team_mode`	No	Team mode — shared completions
`project_id`	Yes	Project ID
`description`	No	Event description
`multi_instance`	No	Multi-instance — each worker gets isolated copy

tascan_create_projectInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	Project name
`location`	No	Project location / venue

tascan_create_workerInspect

Create a new worker (taskee) in the organization

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Worker name
`email`	No	Email
`phone`	No	Phone number

tascan_delete_eventInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID to delete

tascan_delete_projectInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID to delete

tascan_delete_taskInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`task_id`	Yes	Task ID to delete

tascan_dispatch_instructionInspect

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.

ParametersJSON Schema

Name	Required	Description
`ai_agent`	No	Name of the AI agent dispatching (default: TaScan AI)
`issue_id`	Yes	Issue ID this instruction relates to
`send_sms`	No	Send SMS to worker (default: true if phone on file)
`worker_id`	No	Target worker ID (defaults to the worker who reported the issue)
`instruction`	Yes	Clear, actionable instruction for the worker to execute
`remediation_tasks`	No	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`	No	One-line summary for the task list description

tascan_dispatch_to_agentInspect

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.

ParametersJSON Schema

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

tascan_generate_qrInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID

tascan_get_eventInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID

tascan_get_projectInspect

Get details of a specific project

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID

tascan_get_reportInspect

Get completion report for a task list (event) including task status, completions, workers, and photos

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID

tascan_get_taskInspect

Get details of a specific task including completions

ParametersJSON Schema

Name	Required	Description	Default
`task_id`	Yes	Task ID

tascan_list_agentsInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

tascan_list_eventsInspect

List all events (task lists) within a project

ParametersJSON Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID

tascan_list_issuesInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID

tascan_list_projectsInspect

List all TaScan projects in the organization

ParametersJSON Schema

Name	Required	Description	Default
No parameters

tascan_list_tasksInspect

List all tasks in an event (task list)

ParametersJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Task list (event) ID

tascan_list_templatesInspect

List available task templates (built-in and saved)

ParametersJSON Schema

Name	Required	Description	Default
`category`	No	Filter by category (e.g. "live-events", "hospitality", "logistics")

tascan_list_workersInspect

List all workers (taskees) in the organization

ParametersJSON Schema

Name	Required	Description	Default
No parameters

tascan_recommend_fixInspect

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.

ParametersJSON Schema

Name	Required	Description
`ai_agent`	No	Name of the AI agent posting (default: TaScan AI)
`issue_id`	Yes	Issue ID to recommend a fix for
`recommendation`	Yes	The AI-generated recommendation text (clear, actionable instructions)
`structured_recommendation`	No	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 }

tascan_register_agentInspect

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.

ParametersJSON Schema

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

tascan_send_task_emailInspect

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.

ParametersJSON Schema

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

tascan_update_eventInspect

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

ParametersJSON Schema

Name	Required	Description
`name`	No	New name
`list_id`	Yes	Task list (event) ID
`team_mode`	No	Team mode — shared completions
`timer_mode`	No	Timer mode (auto or manual)
`description`	No	New description
`multi_instance`	No	Multi-instance — each worker gets isolated copy

tascan_update_projectInspect

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

ParametersJSON Schema

Name	Required	Description
`name`	No	New name
`status`	No	Status
`end_date`	No	End date (ISO)
`location`	No	New location
`project_id`	Yes	Project ID
`start_date`	No	Start date (ISO)

tascan_update_taskInspect

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

ParametersJSON Schema

Name	Required	Description
`title`	No	New title
`task_id`	Yes	Task ID
`sort_order`	No	Sort position
`description`	No	New description
`response_type`	No	See tascan_add_tasks for guidance. "text" for info collection, "photo" for visual proof, "checkbox" for yes/no only.
`requires_photo`	No	Require photo
`is_safety_checkpoint`	No	Safety-critical flag

tascan_update_workerInspect

Update a worker profile (name, phone, email)

ParametersJSON Schema

Name	Required	Description
`name`	No	New name
`email`	No	New email
`phone`	No	New phone
`worker_id`	Yes	Worker ID

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Server Details

Available Tools

Verify Ownership

Discussions

Your Connectors

Resources