Task lists and tasks in workspaces/shares with statuses, priorities, assignees, dependencies, bulk ops. Call action='describe' for the full action/param reference. Destructive: delete-list, delete-task.
Connector
139,273 tools. Last updated 2026-05-26 10:52
"task management" matching MCP tools:
- Check submissions for a task you published. Use this to see if a human has submitted evidence for your task. You can then use em_approve_submission to accept or reject. Args: params (CheckSubmissionInput): Validated input parameters containing: - task_id (str): UUID of the task - agent_id (str): Your agent ID (for authorization) - response_format (ResponseFormat): markdown or json Returns: str: Submission details or "No submissions yet".Connector
- Refund escrowed funds back to the agent (cancel task). The on-chain flow: Escrow contract -> PaymentOperator.refundInEscrow() -> Agent USDC Use this when a task is cancelled before completion. Only works if funds are still in escrow (not yet released). Args: params: task_id, optional amount (defaults to full bounty) Returns: Transaction result with hash and gas used.Connector
- Submit completed work with evidence for an assigned task. After completing a task, use this to submit your evidence for review. The agent will verify your submission and release payment if approved. Requirements: - You must be assigned to this task - Task must be in 'accepted' or 'in_progress' status - Evidence must match the task's evidence_schema - All required evidence fields must be provided Args: params (SubmitWorkInput): Validated input parameters containing: - task_id (str): UUID of the task - executor_id (str): Your executor ID - evidence (dict): Evidence matching the task's requirements - notes (str): Optional notes about the submission Returns: str: Confirmation of submission or error message. Status Flow: accepted/in_progress -> submitted -> verifying -> completed Evidence Format Examples: Photo task: {"photo": "ipfs://Qm...", "gps": {"lat": 25.76, "lng": -80.19}} Document task: {"document": "https://storage.../doc.pdf", "timestamp": "2026-01-25T10:30:00Z"} Observation task: {"text_response": "Store is open, 5 people in line", "photo": "ipfs://..."}Connector
- Marks the task as `cancelled`. If the task is already in a terminal state (`complete`, `failed`, `expired`), returns 409 Conflict. Only the identity that created the task may cancel it. Use this tool when: - You submitted a probe with `?async=true` and no longer need the result. - You want to free up a pending task before it expires. Do NOT use this tool when: - The task is already complete — cancellation is not possible. Inputs: - `task_id` (path, required): 26-char ULID. Returns: - `task_id` and `status: cancelled`. Cost: - Free. Latency: - Typical: <150ms.Connector
- Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.Connector
Matching MCP Servers
- FlicenseAqualityCmaintenanceEnables AI assistants to manage tasks through a comprehensive interface with 8 tools for creating, updating, searching, and tracking tasks with priorities, categories, and due dates. Features persistent file-based storage, advanced filtering, and task statistics for complete task management workflow.Last updated8
- MIT
Matching MCP Connectors
- Parallel Task MCPOAuth
An MCP server for deep research or task groups
UK pest, disease, and weed management — symptom diagnosis, IPM, approved products
- Update a task. Accepts real task IDs or virtual recurring task IDs (from search_tasks). For recurring tasks, use apply_to to control scope: - "this" (default): Update only this specific occurrence. Materializes virtual tasks automatically. - "all_future": Update the recurrence template. Changes affect all future occurrences. Instance fields (apply_to="this" ONLY): deadline, scheduled_date, has_scheduled_time, has_deadline_time, percent_complete, is_skipped Template fields (apply_to="all_future" ONLY): freq, interval, days_of_week, days_of_month, week_position, months, scheduled_time, deadline_offset_days, deadline_time, is_active Both modes: title, content, priority, duration_minutes, tags Note: is_skipped=true and percent_complete=100 are mutually exclusive. Common operations: - Complete a task: percent_complete=100 - Skip a recurring occurrence: is_skipped=true - Reschedule: scheduled_date="new-date" - Pause a recurrence: apply_to="all_future", is_active=false - Change recurrence pattern: apply_to="all_future", freq=..., days_of_week=...Connector
- Refund escrowed funds back to the agent (cancel task). The on-chain flow: Escrow contract -> PaymentOperator.refundInEscrow() -> Agent USDC Use this when a task is cancelled before completion. Only works if funds are still in escrow (not yet released). Args: params: task_id, optional amount (defaults to full bounty) Returns: Transaction result with hash and gas used.Connector
- Check the current status of a task. The response tells you what action is needed: - "processing": The agent is working. Poll again later. - "awaiting_reply": The agent asked a question. Use agentwork_send_message to reply. - "awaiting_spec_approval": A plan was proposed. Use agentwork_approve_spec to accept/reject. - "awaiting_solution_approval": A solution was proposed. Use agentwork_approve_solution to accept/reject. - "completed": The task is done. Use agentwork_get_task_result to fetch the output. Args: task_id: The task ID returned by agentwork_create_task. api_key: Your Agentwork API key. Returns: JSON with task_id, title, status, and optional question/spec/solution details.Connector
- Rate an AI agent after completing a task (worker -> agent feedback). Submits on-chain reputation feedback via the ERC-8004 Reputation Registry. Args: task_id: UUID of the completed task score: Rating from 0 (worst) to 100 (best) comment: Optional comment about the agent Returns: Rating result with transaction hash, or error message.Connector
- Task-scoped context briefing. Returns a prioritised context payload shaped by your task description, ranked by risk-if-missed. Constraints and alerts rank above general knowledge. Use at the START of reasoning about a question to get the system's best assessment of what's relevant. Complements query_memory: this gives breadth, query_memory gives depth.Connector
- Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.Connector
- Receipted write-through to PlanCrux's log endpoint. Appends a structured log entry to a task with optional evidence references and stage binding. Cannot change task or stage status (human-only), but records work done, findings, and blockers encountered.Connector
- Creates a tester group for a Release Management connected app. Tester groups can be used to distribute installable artifacts to testers automatically. When a new installable artifact is available, the tester groups can either automatically or manually be notified via email. The notification email will contain a link to the installable artifact page for the artifact within Bitrise Release Management. A Release Management connected app can have multiple tester groups. Project team members of the connected app can be selected to be testers and added to the tester group. This endpoint has an elevated access level requirement. Only the owner of the related Bitrise Workspace, a workspace manager or the related project's admin can manage tester groups.Connector
- Get the current escrow payment status for a task. Returns the payment state including: - Authorization status - Amount locked, released, and refunded - Transaction hashes - Current payment strategy Args: params: task_id Returns: Payment status details or "not found" if task has no escrow.Connector
- Discover the best AXIS workflow for a purchasing or compliance task. Free, no auth, and logs lightweight task metadata for intent analytics. Example: task_description='prepare for autonomous Visa checkout'. Use this when you need commerce-specific triage and next-step guidance. Use search_and_discover_tools instead for non-commerce keyword routing across all programs.Connector
- Claim a task. Idempotent: same agent+task returns same execution_id. You execute with your own resources, then call submit_result.Connector
- Cancel a task you published (only if still in 'published' or 'accepted' status). Use this if you no longer need the task completed. Args: params (CancelTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to cancel - agent_id (str): Your agent ID (for authorization) - reason (str): Reason for cancellation Returns: str: Confirmation of cancellation.Connector
- Publish a task to make it visible to operators. Works for both settlementMode='escrow' and 'direct' tasks. The task must be in Draft or Funded status. For escrow Draft tasks: funds are automatically reserved and locked from your wallet (requires sufficient balance). For direct-settlement Draft tasks: no funding happens — the task goes directly from Draft to Published because the client pays the operator on-site (no escrow). This is the intended shortcut for direct-settlement. For Funded tasks (after escrow Quote → Fund flow): the funds are already locked, the task is simply made visible. After publishing, operators can accept the task. Requires authentication. Next: wait for task.accepted via get_task_events or webhook.Connector
- ESCROW FLOW ONLY. For direct-settlement tasks (settlementMode='direct') use acknowledge_direct_settlement_task instead — this endpoint returns 400 with a pointer when called on a direct task. Approve a completed task after reviewing the proof. Triggers payout to the operator. The task must be in UnderReview status AND settlementMode='escrow'. Funds move from locked to earned. Requires authentication.Connector