Skip to main content
Glama
752,342 tools. Updated 2026-11-06 17:04

"Tools for Managing Tasks and Schedules with Apps Like TickTick and Todo" matching MCP tools:

  • Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
    ConnectorNo auth
  • Browse tasks on the marketplace. Defaults to open (``posted``) tasks. Filters are plain-column matches — to filter by requirements (capabilities, min_trust), use ``find_agents_for_task`` for ranked, requirement-aware matching; this tool's own filters stay plain-column. Args: access_token: AgentAuth bearer token (requires ``market.read``). status: Task status to filter on. Defaults to ``"posted"`` (open tasks). Pass any valid status to see tasks in other states. task_type: Optional exact-match task type filter. limit: Maximum results, 1-100. Default 20. Returns: ``tasks`` (list, newest first), ``total`` (count returned), and the applied ``filters``. ``{"error_code": "invalid_input", ...}`` listing the valid values if ``status`` is not a real task status.
    ConnectorNo auth
  • Manage recurring GVT test schedules: add, delete, reset, pause, resume, cancel, and change_frequency. Discover existing schedules and their schids via gvt_list_schedules; control modes require a schid. For one-off tests use gvt_run_visibility_test; for queued batches without recurrence use gvt_run_visibility_batch. Modes: "add" upserts schedules for the provided urls without duplicating; "delete" permanently removes schedule entries by schid or url (test results are never deleted by any mode); "reset" is destructive — deletes all matching schedules first (domain-scoped when provided, otherwise ALL account-wide), then upserts the provided urls; "pause" halts reversibly; "resume" restarts a paused schedule and clears auto-pause reasons and failure counts; "cancel" permanently ends the schedule (schid unusable); "change_frequency" updates the recurrence interval. Management modes (add/delete/reset) require urls; control modes require schid. Subscription-tier enforcement applies.
    Connector
    Destructive
    OAuth
  • Manage recurring GVT test schedules: add, delete, reset, pause, resume, cancel, and change_frequency. Discover existing schedules and their schids via gvt_list_schedules; control modes require a schid. For one-off tests use gvt_run_visibility_test; for queued batches without recurrence use gvt_run_visibility_batch. Modes: "add" upserts schedules for the provided urls without duplicating; "delete" permanently removes schedule entries by schid or url (test results are never deleted by any mode); "reset" is destructive — deletes all matching schedules first (domain-scoped when provided, otherwise ALL account-wide), then upserts the provided urls; "pause" halts reversibly; "resume" restarts a paused schedule and clears auto-pause reasons and failure counts; "cancel" permanently ends the schedule (schid unusable); "change_frequency" updates the recurrence interval. Management modes (add/delete/reset) require urls; control modes require schid. Subscription-tier enforcement applies.
    Connector
    Destructive
    No auth
  • List tasks in a project with optional filters and pagination. Filter by status name, assignee/creator (username or email), tag names and free text.
    ConnectorOAuth
  • Schedules an existing draft video post to publish at a specific future time. Typical flow: create_post_draft first, then schedule_post with the returned post's id. Pass scheduled_for (ISO 8601, at most 1 year out; past times are nudged to now + 30 seconds) or use_next_slot: true to take the next free saved posting time (see get_posting_slots). Pass recurrence to repeat the post on a cadence, like the app's "Repeat this post" (same shape as the public API).
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI assistants with a standardized interface to interact with the Todo for AI task management system. It enables users to retrieve project tasks, create new entries, and submit completion feedback through natural language.
    16 npm
    Apache 2.0

Matching MCP Connectors

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

  • TasksOAuth

    Quadros, pedidos, regras e métricas do trabalho

  • List tasks visible to the caller, with optional filters: projectId, parentId (pass "null" string or JSON null for top-level-only), status, assigneeId (or the sentinels "me" / "unassigned"), assignedToAgentPersona, collaboratorId (or "me": tasks a person collaborates on without holding them), title with titleMode ("contains" default, "equals", "startsWith"; all case-insensitive), dueBefore / dueAfter, overdueOnly, orderBy. Each row carries `collaborators`, the people working on it besides its assignee, isManual and datesFromSubtasks (true when its dates come from its subtasks), and url, the task's link in the Onplana web app. Returns up to 200 tasks per call with cursor-based pagination (nextCursor). Without parentId, matching tasks at every depth are returned, subtasks included; parentId "null" narrows to top-level tasks. PREFER get_plan when you need the whole project tree in one call; PREFER list_assigned_tasks for your own queue. Use list_tasks when drilling parent to children or paginating through a large project. When you pass projectId, the response carries projectResolved: if it is false the id did not match any project visible to you and the empty tasks list says NOTHING about whether that project has work in it, re-check the id (use full ids from list_projects, never abbreviated) rather than concluding the project is empty or unsaved.
    ConnectorOAuth
  • Changes part of a draft's document without resending the rest. The patch is a JSON Merge Patch (RFC 7386): an object shaped like the document naming only what is to change. Three rules and no others -- an object recurses, so {"settings":{"displayComments":false}} changes one switch and leaves the rest of the settings alone; a null removes the member it names, which is the only way to clear the description without restating the document; and everything else replaces, arrays included. That last rule is why this is not the tool for tasks: a tasks array in the patch replaces every task there is. Use it for the name, the description, the settings, the tags and the permissions, and use apply_draft_operations for anything inside tasks, fields, parameters, conditions or notifications. A property the document has no word for is dropped rather than stored, so read the document in the answer rather than assuming the patch landed.
    ConnectorAPI key
  • List account variable NAMES (values are write-only — they are injected into proxy calls and container apps, never read back).
    ConnectorNo auth
  • Screen a person by NAME for bankruptcy exposure ('konkursgjenganger'): leadership roles (chair / managing director) held in companies that later went bankrupt, tenure-weighted, from the dated role history. Use this for HISTORICAL leaders who are no longer in any role index and so cannot be reached via search_persons/get_person. The match is name-based (no national ID), so a hit is a REVIEW FLAG to verify (birth year / address), not a verdict. PII-sensitive — requires the search_full_enabled tier.
    ConnectorNo auth
  • List the third-party apps the user has connected to their Agentcard account via OAuth (e.g. Kilo), including when each was connected and whether it is still active. Read-only. To revoke an app, call revoke_connection with its clientId.
    ConnectorNo auth
  • Beispiel: „Welche Firmen führt eine Person namens Maria Huber?“ Find every company a person runs or represents - across BOTH registers in one call (cross-border person search). Read-only. Parameters: - name (required): person name substring, case-insensitive, e.g. "Mustermann". - country (optional, default "all"): "AT" | "DE" | "all". - page_size (optional, default 25): results per country. - status (optional, default "all"): "active" | "inactive" | "all". Returns the merged search_companies envelope ({countries, results, per_country, notices}) plus ``person_query``; every result card carries ``country``, ``company_id`` and the matched manager. AT matches the primary managing director, DE matches all managing directors AND registered signatories. IMPORTANT: matching is by name and the registers publish birth YEAR only - a shared name across companies or countries does not prove the same person (the notice says so; use birth years and context to corroborate). For general company search use search_companies with other filters; manager_name can be combined there too.
    ConnectorOAuth
  • List the GVT prompt workflows: user-invocable recipes that chain GVT tools into complete tasks (check a page, review a monthly batch, analyze regressions, verify fixes, set up domain monitoring, report client status). Each entry lists its arguments. Use gvt_get_prompt to render a prompt with concrete argument values, then follow the rendered instructions to run the workflow. This catalog is static and costs nothing to call on every session start — it never queues tests or consumes credits.
    ConnectorOAuth
  • List the GVT prompt workflows: user-invocable recipes that chain GVT tools into complete tasks (check a page, review a monthly batch, analyze regressions, verify fixes, set up domain monitoring, report client status). Each entry lists its arguments. Use gvt_get_prompt to render a prompt with concrete argument values, then follow the rendered instructions to run the workflow. This catalog is static and costs nothing to call on every session start — it never queues tests or consumes credits.
    ConnectorNo auth
  • Time report for the project over the last `periodDays` (default 30, max 365): hours planned versus hours actually logged, the billable split, and the tasks where the two diverge most. Planned counts leaf tasks whose plan overlaps the window; worked counts time entries logged inside it. A null KPI means the other side is missing — it is NOT zero, and reporting it as zero turns "nobody planned this" into "the team overshot by 100%". Use it when someone asks how a period went, before writing any status update. Pair it with `get_project_alerts` for the risk side and `get_task_stats` for the delivery side.
    ConnectorOAuth
  • List scheduled pins in this workspace, latest run_at first, with search and filters. Use to find a schedule's id (search its title with q), see what is queued for a period (status=scheduled, sort=run_at_asc), or list failed schedules to retry. For one known schedule use get_schedule; for pins that already published use list_pins. Returns one page: {items, total, limit, offset, has_more}. items are the schedules (id, pinterest_account_id, run_at, status, payload with board_id, title and media, pin_id once it ran, last_error, created_at, updated_at). total counts every match across all pages, so "how many pins are scheduled for next week?" is one call with status=scheduled, since/until and limit=1. To read further, repeat the call with the same filters, q and sort and offset = offset + limit while has_more is true. Fails with account_not_permitted for an account outside the key's allow-list and validation_error for a bad status, sort or timestamp.
    ConnectorAPI key
  • Returns the authenticated PostFlow user with all their permissions and preferences, the subscription of the organization and the scopes of the current token. Call it to verify that the connection works. For the members of the organization call get_organization. token.scopes limits what tools may do: post:publish schedules and publishes posts (without it new posts always wait in review), post:approve approves, rejects and revokes approvals, post:delete deletes posts. Check the scopes before scheduling, approving or deleting.
    ConnectorOAuth
  • Edit a draft or scheduled post before it publishes: set or change scheduled_at (must be in the future), change captions, or replace media. Published or publishing posts can't be edited. Provide at least one of scheduled_at, variant_updates, media_urls. Setting scheduled_at on a draft schedules it: the same checks as create_post apply (plan limits, connected accounts) and the post keeps its id. A caption for a platform with no connected account is left out and listed in skipped.
    Connector
    Destructive
    OAuth
  • Store searches that two to twenty apps all rank for, with each app's position side by side. Use when: "where do we and competitor both rank", "which store keywords does Teams beat Slack on", comparing apps keyword by keyword. Not for: every keyword one app ranks for, use apps_get_keywords. Finding the competitors first, use apps_get_competitors. Returns: List. rows[]: keyword, volume, ranks[] (app_id, rank) in the order the apps were given. Sorted by volume. United States and English only. Cost: 5 + 5 per 100 rows. Default 100 rows = 10 credits. Cached 7 days. Example: {"store": "google_play", "app_ids": ["com.Slack", "com.microsoft.teams"]}
    ConnectorAPI key
  • Start here, and call again whenever a result's meta.catalog_version differs from the one you saw first. Returns every datawebot tool available right now with its input schema, which need sign-in, and how to sign in. Tools added after your session started can be called through run_tool. Free; like every MCP call it needs your datawebot key or connector sign-in.
    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