com.donebear/donebear

Est-ce que com.donebear/donebear est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.donebear/donebear » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 17 outils

• attachment≈ 808 tokens

  Add a file to a task or remove one. `action: "add"` fetches the given HTTPS `url`: the server downloads it, verifies its size and type, and stores it, so the model never sends file bytes. Pass a stable idempotency_key and reuse it for retries so a lost response cannot upload the file twice. `action: "remove"` deletes the named `attachment`. Read a task's files with task_show and `include: ["attachments"]`. Limited to 10 attachments per task and 10 MB per file. Allowed types: images (jpeg, png, gif, webp, heic), PDF, CSV, Markdown, and plain text.

  Paramètres, retour & exemple (8)

  Paramètres

  • url · string · optionnel
    HTTPS URL of the file to attach. Required to add
  • task · string · requis
    Workspace-scoped task number, encoded as a string
  • action · string · requis · add | remove
    Whether to attach a file or delete one
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • filename · string · optionnel
    Display filename on an add; defaults to the URL's last path segment
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • attachment · string · optionnel
    Attachment UUID or prefix (>= 4 chars). Required to remove
  • idempotency_key · string · optionnel
    Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

  Exemple d'appel

  {"name": "attachment", "arguments": {"task": "texte", "action": "add", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "action": "texte", "taskId": "texte", "attachment": "texte"}}

• checklist≈ 799 tokens

  Change the checklist on a task. `action: "add"` appends items, unchecked, after the existing ones: pass every title for a multi-item list in one call (`titles` keeps the given order, while parallel single adds land in arrival order). `action: "edit"` renames an item and/or checks it (`completed: true`) or unchecks it (`completed: false`). `action: "remove"` deletes one. Read the list, with each item's id and state, from task_show.

  Paramètres, retour & exemple (9)

  Paramètres

  • item · string · optionnel
    Checklist item UUID or prefix (>= 4 chars). Required to edit or remove
  • task · string · requis
    Workspace-scoped task number, encoded as a string
  • title · string · optionnel
    One item title to add, or the new title on an edit
  • action · string · requis · add | edit | remove
    What to do to the checklist
  • titles · array · optionnel
    Several item titles to add, kept in the given order (use instead of `title`)
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • completed · boolean · optionnel
    Check (true) or uncheck (false) the item, on an edit
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • idempotency_key · string · optionnel
    Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

  Exemple d'appel

  {"name": "checklist", "arguments": {"task": "texte", "action": "add", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "count": 1, "items": [], "action": "texte", "taskId": "texte"}}

• comment≈ 642 tokens

  Write on a task's comment thread. `action: "add"` posts a comment, attributed to the connected user and visible to everyone in the workspace, so write it as a message to the user's teammates rather than a note to the user; nobody is notified. `action: "edit"` rewrites one of your own (only its author may, and it is then marked edited). `action: "remove"` deletes one permanently — comments have no Trash — so confirm with the user first. Read the thread with task_show and `include: ["comments"]`.

  Paramètres, retour & exemple (7)

  Paramètres

  • body · string · optionnel
    Comment text. Required to add or edit
  • task · string · requis
    Workspace-scoped task number, encoded as a string
  • action · string · requis · add | edit | remove
    What to do on the thread
  • comment · string · optionnel
    Comment UUID or prefix (>= 4 chars). Required to edit or remove
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • idempotency_key · string · optionnel
    Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

  Exemple d'appel

  {"name": "comment", "arguments": {"task": "texte", "action": "add", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "action": "texte", "taskId": "texte"}}

• get_context≈ 1141 tokens

  Get a snapshot of the current workspace: task counts per view, recent open tasks, and every project, label, team and member. This is the tool that answers what is in the workspace and resolves a project, label, team or member by name — there is no separate list tool for those. Use it for that, not as a warm-up before every turn. For tasks themselves use task_list (a view), search (by words) or task_show (one task): the recent tasks here are only the latest few.

  Paramètres, retour & exemple (5)

  Paramètres

  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • timezone · string · optionnel
    IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • tasks_limit · integer · optionnel
    Max recent open tasks to return
  • projects_status · string · optionnel · active | done | archived | all
    Which projects to return

  Exemple d'appel

  {"name": "get_context", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"teams": [], "today": "texte", "labels": [], "members": [], "projects": [], "taskCounts": {}, "viewCounts": {}, "recentTasks": []}}

• guide≈ 681 tokens

  Read Done Bear's guide for one topic: what the data means, how it relates to the rest of the product, and how to use it well. Load a topic before doing that kind of work for the first time in a session. - `views`: Placing a task in Inbox/Today/Upcoming/Anytime/Someday, reading a view, or working out why Today looks wrong. - `dates`: Setting or clearing a due date, or deciding between a deadline and a start date. - `editing`: Changing a task's fields, clearing a value, appending to notes, or moving a task between projects. - `bulk`: Completing, moving, or editing more than one task at a time, or sweeping a whole view. - `checklists`: Adding sub-steps to a task, building a list inside a task, or ticking items off. - `comments`: Discussing a task with teammates: reading its thread, replying, or correcting a comment. - `projects`: Deciding where a task belongs, creating a project or label, changing a project's status, or joining/leaving a project. - `search`: Looking a task up, listing a view, paging through results, or orienting in a new workspace. - `workspaces`: Working across multiple workspaces, hitting a permission or rate-limit error, or making retries safe. - `agents`: Starting work in a Done Bear workspace for the first time. - `importing`: The user asks how to move their tasks in from Todoist, Things, Trello or a CSV.

  Paramètres, retour & exemple (2)

  Paramètres

  • topic · string · requis · views | dates | editing | bulk | checklists | comments | projects | search
    Guide topic to read
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."

  Exemple d'appel

  {"name": "guide", "arguments": {"topic": "views", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"title": "texte", "topic": "texte", "markdown": "texte"}}

• label_create≈ 492 tokens

  Create a new label in the workspace and return its id. Only creates the label: to put it on a task, pass it to task_add `labels` or task_edit `add_labels` afterwards (both take the title). Titles are not unique, so a second call with the same title makes a duplicate — check the labels get_context returns first, and reuse one that already exists.

  Paramètres, retour & exemple (4)

  Paramètres

  • title · string · requis
    Label title
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • idempotency_key · string · optionnel
    Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

  Exemple d'appel

  {"name": "label_create", "arguments": {"title": "texte", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "title": "texte"}}

• project≈ 679 tokens

  Create or change a project. `action: "add"` creates one (name required). `action: "edit"` updates the named project: only the fields given change, and an empty string clears description or target_date. `action: "join"` puts it in the caller's Your projects sidebar list and `action: "leave"` takes it out. Read projects with get_context.

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · optionnel
    Project name. Required on add; a rename on edit
  • action · string · requis · add | edit | join | leave
    What to do with the project
  • status · string · optionnel · active | on_hold | done | cancelled
    Project status (edit only)
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • project · string · optionnel
    Project id, key, or name. Required for edit, join and leave
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • description · string · optionnel
    Project description (empty string clears it on an edit)
  • target_date · string · optionnel
    Target date (YYYY-MM-DD), or an empty string to clear it (edit only)
  • idempotency_key · string · optionnel
    Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

  Exemple d'appel

  {"name": "project", "arguments": {"action": "add", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "key": "texte", "name": "texte", "action": "texte"}}

• search≈ 1067 tokens

  Search tasks across the workspace. Ranked lexical search over title and description: exact and prefix matches rank first, then word-boundary, substring, and fuzzy matches, with recency and status factored in. Multi-word queries match in any order. Searches every state by default, completed and archived included. Use this when the user names a task by its words; use task_list to browse a view (Today, Inbox, …) and task_show once you have the task number.

  Paramètres, retour & exemple (7)

  Paramètres

  • limit · integer · optionnel
    Max results
  • query · string · requis
    Search query (matches title and description)
  • state · string · optionnel · open | done | archived | all
    Filter by task state
  • cursor · string · optionnel
    Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • timezone · string · optionnel
    IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

  Exemple d'appel

  {"name": "search", "arguments": {"query": "texte", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "query": "texte", "tasks": [], "total": 1, "hasMore": true, "nextCursor": "texte"}}

• task_add≈ 1079 tokens

  Create a new task. An explicit `when` selects its start placement: today, inbox, upcoming, anytime, or someday; upcoming schedules tomorrow. Without `when`, a `deadline` or omitted `timezone` selects anytime first. Otherwise, a `project` or `team` selects inbox; an unfiled task selects today. Pass the user's known IANA `timezone` to resolve calendar days. Use `when: "inbox"` for capture without a commitment to today. `deadline` uses YYYY-MM-DD. Optionally assign the task, attach existing labels, or pass checklist item titles in `checklist`; their order is preserved. The result's `view` reports the selected start placement, while a due or overdue deadline can make the task appear in Today. To change an existing task, use task_edit for fields or the available checklist tools for items. Search first when the user may be describing an existing task.

  Paramètres, retour & exemple (13)

  Paramètres

  • team · string · optionnel
    Team id, key, or name
  • when · string · optionnel · inbox | anytime | today | upcoming | someday
    GTD view bucket: today, inbox, upcoming, anytime, someday. Omitting this means today, with three exceptions: a deadline or a missing timezone falls back to anytime (the work is due later, or today cannot be resolved), and a project or team falls back to inbox (the task is already filed). Pass timezone to get today. Use "inbox" for a capture the user has not committed to doing.
  • notes · string · optionnel
    Task description/notes
  • title · string · requis
    Task title
  • labels · array · optionnel
    Labels to attach (each a label id, title, or id prefix)
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • project · string · optionnel
    Project id, key, or name to assign this task to
  • assignee · string · optionnel
    Member (user id, name, or email) or task agent (id or name) to assign the task to
  • deadline · string · optionnel
    Due date in YYYY-MM-DD format
  • timezone · string · optionnel
    IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
  • checklist · array · optionnel
    Checklist item titles to create on the task, kept in the given order
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • idempotency_key · string · optionnel
    Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

  Exemple d'appel

  {"name": "task_add", "arguments": {"title": "texte", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "ok": true, "view": "inbox", "title": "texte", "number": 1, "checklistCount": 1}}

• task_agent_get≈ 873 tokens

  Read the task-agent identity bound to this connection's existing API key in one explicit workspace. Returns only key metadata and the exact agent UUID or null; an inactive agent includes disabledAt. Requires an API-key connection and current workspace membership. Does not register, assign or start any task. Use this before task_agent_register and retain key.id as expected_key_id.

  Paramètres, retour & exemple (2)

  Paramètres

  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace_id · string · requis

  Exemple d'appel

  {"name": "task_agent_get", "arguments": {"context": "texte", "workspace_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "key": {}, "agent": "texte", "created": true, "workspaceId": "texte"}}

• task_agent_register≈ 989 tokens

  Explicitly register one assignable task agent for this connection's existing key in one workspace, after the user approves that durable binding. Requires a write-scoped API key restricted to exactly this workspace and an owner/admin membership. Read task_agent_get first and pass its key.id as expected_key_id. Same key/workspace/name retries return the same UUID; conflicting or inactive bindings fail without takeover or reactivation. Creates no key, changes no scope, and does not assign/import/start tasks.

  Paramètres, retour & exemple (4)

  Paramètres

  • name · string · requis
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace_id · string · requis
  • expected_key_id · string · requis

  Exemple d'appel

  {"name": "task_agent_register", "arguments": {"name": "texte", "context": "texte", "workspace_id": "texte", "expected_key_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "key": {}, "agent": "texte", "created": true, "workspaceId": "texte"}}

• task_archive≈ 631 tokens

  Archive a task, or several at once with `tasks` (max 50). They move to the Trash view, out of every working list, and stay readable there (task_list `view: "trash"`). Archiving is not completing: use task_done for work that was finished, and task_archive only for tasks the user wants gone. Confirm with the user first.

  Paramètres, retour & exemple (4)

  Paramètres

  • task · string · optionnel
    Workspace-scoped task number, encoded as a string
  • tasks · array · optionnel
    Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

  Exemple d'appel

  {"name": "task_archive", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "count": 1, "tasks": [], "action": "texte"}}

• task_done≈ 669 tokens

  Mark a task as complete, or several at once with `tasks` (max 50). They move to the Logbook view. A set of 50 is undone one task_reopen call at a time, so confirm the list with the user first.

  Paramètres, retour & exemple (5)

  Paramètres

  • task · string · optionnel
    Workspace-scoped task number, encoded as a string
  • tasks · array · optionnel
    Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • expectedRevision · integer · optionnel
    Complete only the reviewed task revision from task_show or task_list. Use with task, not tasks. A changed task returns a conflict; reload and review before trying again.

  Exemple d'appel

  {"name": "task_done", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "count": 1, "tasks": [], "action": "texte"}}

• task_edit≈ 1102 tokens

  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.

  Paramètres, retour & exemple (15)

  Paramètres

  • task · string · optionnel
    Workspace-scoped task number, encoded as a string
  • team · string · optionnel
    Team id, key, or name
  • when · string · optionnel · inbox | anytime | today | upcoming | someday
    Move to a different GTD view
  • clear · array · optionnel
    Fields to remove a value from, e.g. ["deadline"]. Use this rather than sending an empty string.
  • notes · string · optionnel
    New description/notes (replaces existing)
  • tasks · array · optionnel
    Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
  • title · string · optionnel
    New title
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • project · string · optionnel
    Project id, key, or name
  • assignee · string · optionnel
    Assign to a member (user id, name, or email) or a task agent (id or name)
  • deadline · string · optionnel
    Set due date (YYYY-MM-DD)
  • timezone · string · optionnel
    IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
  • add_labels · array · optionnel
    Labels to attach (each a label id, title, or id prefix). The label has to exist already — create one with label_create
  • remove_labels · array · optionnel
    Labels to detach (each a label id, title, or id prefix)

  Exemple d'appel

  {"name": "task_edit", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "count": 1, "tasks": [], "action": "texte"}}

• task_list≈ 1175 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • view · string · optionnel · inbox | anytime | today | upcoming | someday | logbook | trash
    Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`
  • limit · integer · optionnel
    Max results
  • state · string · optionnel · open | done | archived | all
    Filter by task state
  • cursor · string · optionnel
    Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
  • search · string · optionnel
    Ranked lexical search over title/description; when set, results are ordered by relevance instead of recency
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • timezone · string · optionnel
    IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

  Exemple d'appel

  {"name": "task_list", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "tasks": [], "total": 1, "hasMore": true, "nextCursor": "texte"}}

• task_reopen≈ 582 tokens

  Reopen a completed task, or several at once with `tasks` (max 50). Each returns to its previous view.

  Paramètres, retour & exemple (4)

  Paramètres

  • task · string · optionnel
    Workspace-scoped task number, encoded as a string
  • tasks · array · optionnel
    Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

  Exemple d'appel

  {"name": "task_reopen", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "count": 1, "tasks": [], "action": "texte"}}

• task_show≈ 1228 tokens

  Get full details for a single task: its fields, labels and checklist items, by workspace-scoped task number. Add `include` for the parts that cost extra reads: `["comments"]` for the discussion thread (oldest first, with author and whether each was edited) and `["attachments"]` for the files on it, each with a short-lived signed URL.

  Paramètres, retour & exemple (5)

  Paramètres

  • task · string · requis
    Workspace-scoped task number, encoded as a string
  • context · string · requis
    Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • include · array · optionnel
    Extra sections to load. Omit unless you need them: each is its own round trip
  • timezone · string · optionnel
    IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
  • workspace · string · optionnel
    Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

  Exemple d'appel

  {"name": "task_show", "arguments": {"task": "texte", "context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"task": {}, "labels": [], "comments": [], "attachments": [], "checklistItems": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.donebear.com/mcp