Skip to main content
Glama
683,149 tools. Updated 2026-10-21 04:22

"A checklist for various tasks or activities" matching MCP tools:

  • Declares worked time on a project task or an activity for the given days. This performs a real write - use deliberately. taskId comes from list_timesheet_tasks - call it first. On regular tasks and activities a day never holds more than 1 day of work, so a quantity can be silently reduced: always report the quantities the response says were recorded. Exceptional tasks are exempt - uncapped, and not counted towards the day. Read get_documentation('timesheets') for the caps and the refusals.
    ConnectorOAuth
  • Add a list of up to 50 tasks to an existing Onplana project in one call, at the project root or under a sprint / epic. Fits "add these tasks to my launch project" or a checklist pasted into the chat. Single transaction (all-or-nothing), in place of calling create_task N times; add_subtasks covers new tasks that are children of an existing task. THIS TOOL DOES NOT SCHEDULE. Tasks land with NO dates unless startDate and dueDate are set on each one, and there is no way to express durations or predecessors here at all. A schedule (phase durations, effort estimates, "task 5 depends on task 3", a critical path) sent through this tool arrives as a flat dateless list, and the Gantt, timeline and critical path are all empty. Use instantiate_plan instead, which takes estimatedDays per task and computes real start and due dates from them. It accepts a projectId, so it works on a project that already exists. Neither tool accepts predecessors: create the tasks first, then add each dependency with link_dependency. The result includes `url` for the project (and one per task). ALWAYS show the project link in your reply so the user can open what you just created.
    ConnectorOAuth
  • List tasks in the workspace, most recently updated first. Completed tasks are ordered by completion time, newest first. Filter by view (inbox, today, upcoming, anytime, someday, logbook, trash) and/or state (open, done, archived, all); `search` ranks matches within that filter. `view: "logbook"` reads completed tasks and `view: "trash"` archived ones, whatever `state` says. Returns up to `limit` tasks; `hasMore` is true when more matched than were returned, and passing `nextCursor` back as `cursor` reads the next page. To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.
    ConnectorNo auth
  • Update fields on one task (`task`) or on several at once (`tasks`, max 50). Only the provided fields are changed; omitted fields are left untouched. To remove a value, list the field in `clear` (e.g. `clear: ["deadline"]`). Notes replace the existing notes (no append). `assignee` assigns the task; clear it to unassign. `add_labels` and `remove_labels` change which labels are on it. Editing several tasks applies the same changes to every one of them and cannot be undone in one call, so confirm the list with the user first. For status changes use task_done, task_reopen or task_archive, and for checklist items use the available checklist tools; this tool does not change either.
    Connector
    Destructive
    No auth
  • List tasks in the workspace, most recently updated first. Completed tasks are ordered by completion time, newest first. Filter by view (inbox, today, upcoming, anytime, someday, logbook, trash) and/or state (open, done, archived, all); `search` ranks matches within that filter. `view: "logbook"` reads completed tasks and `view: "trash"` archived ones, whatever `state` says. Returns up to `limit` tasks; `hasMore` is true when more matched than were returned, and passing `nextCursor` back as `cursor` reads the next page. To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.
    ConnectorNo auth
  • Update fields on one task (`task`) or on several at once (`tasks`, max 50). Only the provided fields are changed; omitted fields are left untouched. To remove a value, list the field in `clear` (e.g. `clear: ["deadline"]`). Notes replace the existing notes (no append). `assignee` assigns the task; clear it to unassign. `add_labels` and `remove_labels` change which labels are on it. Editing several tasks applies the same changes to every one of them and cannot be undone in one call, so confirm the list with the user first. For status changes use task_done, task_reopen or task_archive, and for checklist items use the available checklist tools; this tool does not change either.
    Connector
    Destructive
    No auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    MCP server that provides read-only access to cached metadata of public activities, contests, and competitions from multiple sources via SQLite, enabling search and listing without hitting external sites.
    1
    -

Matching MCP Connectors

  • Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off.

  • Oregon DMV MCP — live wait times at all 60 Oregon DMV field offices, plus the office

  • Create a task. Link it to an epic with `epicId` (omit for a standalone task). `status` defaults to 'open'. Adding an open task to a finished epic ('acceptance'/'ready') sends it back to 'designed' — don't add follow-up work there; use a standalone task or a new epic instead. Never create tasks for deploying/rolling out or for an acceptance checklist. If the user is working inside a VSCode workspace and a `<workspace>/.bilg/bilg.config.json` exists, prefer that file's `projectName` over the API key's default project. Descriptions are summaries. If the task has a detailed spec, create a document and link it with documentId. Work only on items assigned to the user unless told otherwise; see list_tasks assignee='me'. When setting status to 'blocked', include a blockedReason. Don't invent priority — leave it unset if unknown.
    ConnectorAPI key
  • Search current enrichment provider records by natural-language interests in a required region: pass the place the family names (city, neighborhood or area) or a region ID. Jev maps it onto a covered region in parallel with the activities, and the response region is the region searched; call list_regions only after LOCATION_UNSUPPORTED. Location words in the query are not used for filtering. Jev maps the query onto specific activities, PostgreSQL retrieves up to 120 providers in the region tagged with those activities, and Jev ranks them by relevance. Returns selected_types, relevance scores and limitations; does not verify program availability. All callers share the same search rate and concurrency limits. Search text is processed by Jev; operational search analytics are stored. Do not include child names or private details.
    ConnectorNo auth
  • Search current enrichment provider records by natural-language interests in a required region: pass the place the family names (city, neighborhood or area) or a region ID. Jev maps it onto a covered region in parallel with the activities, and the response region is the region searched; call list_regions only after LOCATION_UNSUPPORTED. Location words in the query are not used for filtering. Jev maps the query onto specific activities, PostgreSQL retrieves up to 120 providers in the region tagged with those activities, and Jev ranks them by relevance. Returns selected_types, relevance scores and limitations; does not verify program availability. All callers share the same search rate and concurrency limits. Search text is processed by Jev; operational search analytics are stored. Do not include child names or private details.
    ConnectorNo auth
  • List the caller's open sales tasks (activities of type 'task' not yet done), bucketed overdue / today / upcoming and ordered most-urgent-first with per-bucket counts. Close one with complete_sales_task.
    ConnectorNo auth
  • Get the user's open (unchecked) checklist items across all unarchived notes, each with its note ID and title. Call this at the start of a session to pick up tasks the user left for you — items you can act on, act on; check them off with check_item when done.
    ConnectorAPI key
  • Returns the Hermès Birkin authentication checklist: hardware engraving, blind-stamp year decode, saddle stitching, leather-specific tells, and recommended professional authenticators. Call this for 'is this real', 'how to spot a fake', 'is it authentic', 'what should I check'. NEVER declare a bag real or fake yourself — quote the checklist and recommend a pro authenticator at the end.
    ConnectorNo auth
  • Use this when the user asks which Familia households, families, or shared boards are available. Includes member names and user ids for assigning tasks or plans. Do not use for listing tasks, plans, or calendar events.
    ConnectorNo auth
  • Use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items. If the same list task repeats across several days, weeks, or months, provide repeatRule and create one recurring list task instead of multiple one-time tasks. Do not use when editing an existing list attachment. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.
    Connector
    Destructive
    No auth
  • Set up a new estate for the signed-in user and generate their personalized probate checklist. Use this when list_my_estates returns no estates (or one with no deceased details yet), or the user is just getting started. Saves estate details and placeholder assets, then starts checklist generation that may research public sources and send a completion email. Refuses an already-onboarded estate. Collect the fields conversationally first, then call once; partial failures are not guaranteed safe to retry.
    Connector
    Destructive
    No auth
  • YOUR OWN checklist ('Your list'), ONE section of the Morning Desk: open tasks first (with their optional ticker and due date), then recently checked-off ones. Returns each task's id, which the other task tools take. Not the whole desk: for that, use get_morning_desk. Private to you.
    ConnectorOAuth
  • Produce a focused pull-request review checklist for a language or stack. FREE. Covers the things that actually break in production, with extra items per language. Typical input {"language": "python"} returns {"language": "python", "checklist": ["...", ...], "note": "..."}. Use before a review, to decide what to look for. Not for reviewing actual code - pass code to review_diff or security_deep_dive. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Produce a focused pull-request review checklist for a language or stack. FREE. Covers the things that actually break in production, with extra items per language. Typical input {"language": "python"} returns {"language": "python", "checklist": ["...", ...], "note": "..."}. Use before a review, to decide what to look for. Not for reviewing actual code - pass code to review_diff or security_deep_dive. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • REQUIRED when coaching setup. Return the ordered Protocol checklist for a module. For 95/5 / share transfer into the Trust use equity_95_5 (not a freestyle solicitor checklist). Modules: vault, trs, equity_95_5, psc, banking, ip, philosophy, legacy, property.
    ConnectorNo auth
  • Generate a participant HANDOUT or reference material for ONE activity using Metodic's real generator, and return it as a branded HTML artifact in the chat (also saved to the session). Unlike a worksheet (which participants fill in), a handout is READING/REFERENCE material the participant keeps beside their worksheet — background, a framework, a case study, a persona, a checklist. Give the activity's number (1-based) and optionally a `kind`. Framing activities (Opening/Closing) can have handouts too. Takes ~15-30s and ~0.5 Metodic credit.
    ConnectorNo auth
  • Lists what an employee may declare time on for a given month: the project tasks they are assigned to and the non project activities such as leave, absence or training. Every taskId is what declare_time expects. Listing a task is not permission to declare on it: get_timesheet's rights.canEdit says whether the period still accepts one. An affectation range can cover only part of the month. Read get_documentation('timesheets') before declaring.
    ConnectorOAuth