Skip to main content
Glama
473,139 tools. Updated 2026-08-24 16:54

"task management" matching MCP tools:

  • Permanently delete a task. Comments and attachments are removed automatically. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).
    Connector
  • Shared task tracker (TAPI) with append-only history. Single entry point — pick an operation. list = overview with computed status/completion (roots only by default). get = slug|id → single task + architecture versions. history = slug|id → full history, with_content=true fetches MD from S3. create = slug+title(+description, parent_id, related_to, tags, scope). add_history = slug|id+type+summary — the primary way to report progress, notes, snippets, blockers and architecture docs; supports snoozed_until. update = slug|id + any of title/description/parent_id/related_to/tags — metadata only, logs an audit note; status and completion stay history-driven via add_history. delete = slug|id+confirm:true — soft delete, refused while the task has children. search = AND-match on distinctive words across title/description/slug + history summaries. export = Markdown overview grouped by status.
    Connector
  • Delete a use case from a draft UT, including every task inside it. Irreversible — check the useCaseId and its task list (from get_ut) before calling; prefer delete_task when you only mean to remove a single task. Only works on PREPARING drafts.
    Connector
  • List pages in Redpanda API reference documentation. Returns endpoints, schemas, and topic pages with URL, title, type, and description. SCOPING (important for accurate results): - api="all" or omit: Lists all available APIs - api="admin": Cluster management operations (brokers, partitions, configs, users) - api="cloud-controlplane": Redpanda Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Cloud cluster data operations (topics, ACLs, connectors) - api="http-proxy": Kafka operations over HTTP (produce, consume, offsets) - api="schema-registry": Schema management (register, retrieve, compatibility) Use this to browse API structure. For general Redpanda docs, use ask_redpanda_question instead.
    Connector
  • Cancel a task you posted. Only legal before bidding/assignment closes it out. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task to cancel. Returns: The cancelled task on success. ``{"error_code": "not_found", ...}`` if the task doesn't exist, ``{"error_code": "authorization_failed", ...}`` if you're not the poster, or ``{"error_code": "invalid_input", ...}`` if the task is already past the cancellable stage.
    Connector
  • Bid on an open task. Args: access_token: AgentAuth bearer token (requires ``market.bid``). task_id: UUID of the task to bid on. proposed_cost_units: Your price, as an **integer** amount_units. Never a float or Decimal — money is integer units end to end. estimated_duration_seconds: How long you expect the work to take. proposed_approach: Free-text summary of how you'll do the work. terms: Optional JSONB — anything else worth stating up front. confidence_score: Your self-assessed confidence, 0.0-1.0. Returns: The created bid (status ``"pending"``). The task moves to ``"bidding"`` on its first bid. Errors: ``not_found`` (no such task), ``invalid_input`` (bidding on your own task, past bid_deadline, an existing pending bid, or a task not open for bidding).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Review the assignee's latest submitted result. One tool, three actions — not three tools (PLAN.md §5). - ``accept``: task -> completed. Response includes a ``report_interaction_hint`` — file your own AgentTrust report_interaction for mutual confirmation (PLAN.md §7.4); the marketplace already files its own first-party report. - ``reject``: task -> failed (terminal — not a revision request). Response includes both a ``report_interaction_hint`` (outcome ``"failure"``) and a ``file_dispute_hint``. - ``request_revision``: task -> in_progress. The assignee resubmits via ``submit_result``. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task under review. action: One of ``accept``, ``reject``, ``request_revision``. reviewer_notes: Optional free-text feedback, recorded on the result. Returns: ``{"task": ..., "result": ...}`` plus hints on accept/reject. Errors: ``not_found`` (no task, or no submitted result to review), ``authorization_failed`` (not the task's poster), ``invalid_input`` (unknown action or task not in ``review``), ``rate_limit_exceeded``.
    Connector
  • Move tasks and all their subtasks to another tasklist, preserving the parent/child structure. Subtasks move with their parent automatically, so only the topmost task of each subtree needs to be listed. A task whose parent is not part of the move is detached from it, becoming a top-level task in the destination.
    Connector
  • WHEN: user asks to create a DevOps Task or start development on a Work Item. Triggers: 'create task', 'créer une tâche', 'start development on', 'commencer le dev sur', 'créer un task ADO', 'new development task for WI'. Create a D365 F&O development Task work item in Azure DevOps following the project naming convention. Rules applied automatically based on the parent work item: (A) Parent title starts with a project prefix + digits (FDD/RDD/IDD/CR/...) => Task named '{Prefix} - N - {Title}', Task is child of that WI, branch '{Prefix}_Task_{id}'. (B) Selected WI is related to a prefixed WI (e.g. a Bug linked to a CR) => Task is child of the prefixed WI, Bug is 'related' to the Task, same naming. (C) No prefixed relation => Task named '{3-letter-type}{wiId} - N - {Title}', child of selected WI, branch '{3-letter-type}{wiId}_Task_{id}'. The N counter increments automatically based on existing sibling tasks. A Git branch is created automatically in the repository. Assignee and CC list are embedded in the task description. LANGUAGE RULE: write the 'description' (Proposed Solution) in the same language the user used in their request. Default is English. If the user wrote in French, write the solution in French. Static section labels (headers, field names) remain in English. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Work Items: Read & Write, Code: Read & Write).
    Connector
  • Creates a new household task. Only title is required; the task starts unassigned and uncompleted. Use assign_task, update_task, or complete_task to change it afterward.
    Connector
  • Soft-deletes a task: it stops appearing in list_tasks but the record is retained rather than permanently removed. Fails if the task was already deleted.
    Connector
  • Reopens a completed task, clearing its completion timestamp and completed-by user. Fails with a conflict if the task is not currently completed.
    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
  • Retrieve the list of tables configured in the app, used for restaurant mode or table management.
    Connector
  • Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date. Pass deal_id and/or lead_id (each must be owned by the caller). type defaults to 'note'; for a task set type='task' and a due_date (YYYY-MM-DD). Tasks appear in list_sales_tasks.
    Connector
  • Look up a hotel booking by its management token (sent in the confirmation email). Returns the booking status, hotel, dates, and guest details.
    Connector
  • Return the Knox MCP server self-description: operator, USPTO patent reference, jurisdiction, available tools, and links to the public AAM (Agent Audit and Management) documentation surface.
    Connector
  • Answer one A2A task you pulled with a2a_get_messages, completing it. Authorised by ownership, not by holding the task id: a task you were not addressed is not found. A completed task cannot be answered twice.
    Connector