AgentMarketMCP / SKILL 资产档案馆

目录 / dutify-mcp

MCP 鉴权未知 未评级 已上架

dutify-mcp

Bridges an AI agent to the Dutify suite — project management, wiki (Codexum) and feature requests (Roadmarq). Tasks, spaces, lists, views, custom fields, comments and webhooks over one API key. Agents get a real seat with scoped permissions rather than a bolt-on integration, so they act on the same workspace context the team works in. Authentication: send your Dutify PM API key (dk_live_…) as the X-API-Key header. A key is bound to one workspace; X-Dutify-Workspace optionally selects it by name or id.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链
模型生成摘要（rules/v1 · 2026-09-27 16:29）：Bridges an AI agent to the Dutify suite — project management, wiki (Codexum) and feature requests (Roadmarq)
这是模型对公开材料的总结，不是官方声明，请以原链内容为准。

接入信息

传输形态
http
鉴权方式
鉴权未知
端点
https://dutify-mcp--dutify.run.tools
鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段
{
  "mcpServers": {
    "dutify-mcp": {
      "url": "https://dutify-mcp--dutify.run.tools"
    }
  }
}

能力清单

工具说明
whoamiReturns the calling API key’s identity — workspace it is bound to, scopes it carries, and the configured backend URLs. Resolves the bound workspace via PM `GET /v1/api-keys/current` (a fresh HTTP call on every identity check). Safe to call as a session sanity check.
list_accountsList the accounts configured for this MCP session. Returns one entry per account with `name` (the label the caller passes as the `account` tool argument) and `workspace` (the workspace identifier or name declared for that account). API keys are not returned. In single-account mode (X-API-Key with optional X-Dutify-Workspace), returns a single entry with name="default". In multi-account mode (X-Dutify-Accounts header), returns every configured account. Call this first when you do not know which account names are available.
find_my_workspaceSelf-introspect the API key: returns the bound workspace identifier+name and the scopes the key carries, in a single PM `GET /v1/api-keys/current` call (no probing). Workspace tools discover this automatically when X-Dutify-Workspace is omitted. Cached per key for an hour.
list_workspacesINFORMATIONAL ONLY — list every workspace the underlying user (the human who created this API key) is a member of. IMPORTANT: an API key is bound to EXACTLY ONE of these workspaces — only that one will accept requests. You cannot switch between workspaces within a session. To act on a different workspace, the user must provision a separate API key for it and reconfigure the MCP client. The `bound` field on each entry indicates whether it matches the API key's bound workspace (resolved via `/v1/api-keys/current`).
list_boardsList feature-request boards the caller can view in the current workspace. Each entry includes the board slug and the short-ID prefixes (featureRequestKey, bugReportKey) needed to address requests/bugs in follow-up tool calls.
list_spacesList wiki spaces the caller can view in the current workspace, each with a page count. Use the `key` field as the space identifier in follow-up wiki tool calls.
get_endpoint_examplesFetch the request/response example payloads (full JSON values) for a Dutify API resource tag. Use this when you're about to write rich content via a tool that accepts a TipTap `content` parameter (e.g. wiki_create_page) and need a concrete reference of what the doc shape looks like — banners, collapsibles, mermaid diagrams, code blocks with language, mentions, inline labels, tables, task lists, etc. Pass the resource tag (e.g. "Wiki Pages (Lite)", "Milestone Articles"). Optionally narrow with `operationId` (e.g. "createPage") and `name` (e.g. "full" or "full-tiptap") — both names appear in the per-tag detail response so an agent can pick exactly the example it needs without paying tokens for the rest. Returns the catalog JSON; the example payloads are under `operations[*].requestBodyExamples[name].value`. Tag list (lightweight) is at GET /v1/api-catalog. Per-tag detail (schemas, no example bodies) is at GET /v1/api-catalog/{tag}. This tool calls the third tier — GET /v1/api-catalog/{tag}/examples — which carries the heavy payloads.
wiki_searchFind wiki PAGES by title/keyword in the current workspace. Returns a list of matching pages (slug, title, spaceKey, spaceName, excerpt, status, updatedAt) — no UUIDs, no full body. Use this to LOCATE or LIST pages (then call wiki_get_page to read one). To ANSWER a question FROM wiki content — i.e. get back quotable passages with citations and relevance scores — use wiki_retrieve instead. Optionally scope to a single space by passing spaceKey. Defaults to hybrid (keyword + semantic) ranking; pass mode to override. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:search:read`.
wiki_retrieveSearch the wiki by MEANING and get back the most relevant PASSAGES (chunks) with citations and relevance scores. Use this to GROUND or ANSWER a question from wiki content: it returns quotable chunkText plus the source page/section so you can cite it. Each result has pageSlug, pageTitle, spaceKey, spaceName, chunkIndex, headingPath (heading-path breadcrumb), chunkText, score (0..1, higher = more relevant), status and updatedAt. This is retrieval-augmented generation (RAG) over wiki content, NOT a page finder — to merely LOCATE or LIST pages by title/keyword use wiki_search. Defaults to the top 5 chunks; pass limit to widen. Fails open to keyword retrieval if the embedding provider is unavailable. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:search:read`.
wiki_list_pagesList wiki pages in a space. Without `parent` returns root-level pages; pass a parent slug to list that page's children. Response items have slug, title, status, type (page|folder), parentSlug, updatedAt — no bodies. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:pages:read`.
wiki_get_pageGet a wiki page by slug within a space. Default format is Markdown (the body is returned under the `markdown` field); pass format="tiptap" for raw ProseMirror JSON. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:pages:read`.
wiki_create_pageCreate a wiki page under a space. Pass EITHER `markdown` (simpler, server converts to TipTap) OR `content` (TipTap/ProseMirror JSON, mutually exclusive with markdown). Use `content` when you need rich features that markdown can't express — banners, collapsibles, mermaid diagrams, action buttons, inline labels, mentions, code blocks with language, etc. For the full TipTap doc shape and a copy-friendly reference of every node and mark, call `get_endpoint_examples` with tag="Wiki Pages (Lite)" (and optionally name="full-tiptap"). Optional parent slug to nest under another page. Returns the created page DTO. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:pages:write`.
wiki_update_pageUpdate an existing wiki page by slug. Any field left unset preserves the current value. Pass EITHER `markdown` OR `content` (TipTap/ProseMirror JSON) for the body — they're mutually exclusive. Use `content` for rich features (banners, collapsibles, mermaid, etc.); call get_endpoint_examples(tag="Wiki Pages (Lite)") for the full doc shape. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:pages:write`.
wiki_move_pageMove a wiki page to a new parent and/or a new space. All body fields are optional and use slugs (resolved server-side in the target space) instead of UUIDs: `targetSpaceKey` for cross-space moves (omit to stay in the current space); `newParent` is the slug of the new parent page (omit/null to move to space root); `afterPage` is the slug of the sibling page to insert after (omit/null to place first). Returns the moved page DTO. Page results include webUrl: a browser link requiring normal workspace access. Use it for citations; it does not make the page public. API-key scope: `wiki:pages:write`.
wiki_delete_pageArchive (soft-delete) or permanently delete a wiki page by slug. Falls through to the non-lite Wiki Pages API since there is no lite delete endpoint — path is `DELETE /v1/workspaces/{workspaceIdentifier}/wiki/spaces/{spaceKey}/pages/{slug}` with optional `?permanent=true`. Default behavior archives the page (soft delete); pass `permanent: true` to hard-delete (requires admin access). Returns 204 on success. API-key scope: `wiki:pages:write`.
wiki_get_page_shareGet the public SHARE-LINK status for a single page (PublicShareInfoDTO): `isEnabled`, `publicToken`, `publicUrl` (the shareable link), `showAuthor`, `sharedAt`, `sharedBy`, `workspaceAllowsSharing`. A per-page share link lets anyone with the URL read just that one page — distinct from publishing a whole space (wiki_set_public_settings). Requires edit access. API-key scope: `wiki:pages:read`.
wiki_enable_page_shareEnable a public SHARE LINK for a single page, returning a PublicShareInfoDTO with the `publicUrl` to hand out. Optional `token` sets a custom URL slug (3-100 chars, lowercase letters/digits/hyphens; 409 if already taken — omit to auto-generate). Optional `showAuthor` toggles author display. ⚠️ OUTWARD-FACING: anyone with the link can read this page — confirm with the user before enabling. Requires edit access. API-key scope: `wiki:pages:write`.
wiki_disable_page_shareDisable the public share link for a single page, revoking access via its URL (returns 204). Requires edit access. API-key scope: `wiki:pages:write`.
wiki_list_spacesList every wiki space the caller can see in the current workspace. Each entry has the space's `key` (use this in subsequent calls), `name`, `description`, `effectivePermission` (view/edit/admin), and `canView`/`canEdit`/`canAdmin` booleans for quick gating. Call this first when an agent needs to figure out which space a wiki action should target. API-key scope: `wiki:spaces:read`.
wiki_get_spaceFetch a single wiki space by key. Returns the WikiSpaceDTO (id, key, name, description, icon, color, cover image, visibility flags, permissions, timestamps). For the page tree inside the space, use wiki_get_space_with_pages instead. API-key scope: `wiki:spaces:read`.
wiki_get_space_with_pagesFetch a wiki space AND its complete page tree in one call. Returns WikiSpaceWithPagesDTO — space metadata plus `pages` (a recursive tree of WikiPageTreeNodeDTO with slug, title, type=page|folder, hasChildren, children[], view count, top reactions, the caller's effectivePermission per node). Use this to render or traverse the whole space; for a single level (root or one parent's children) wiki_list_pages is lighter. API-key scope: `wiki:spaces:read`.
wiki_create_spaceCreate a new wiki space in the current workspace. `key` is the unique short identifier used in URLs and subsequent API calls — uppercase letters + digits only, 2-20 chars, must start with a letter (e.g. "DOCS", "ENG2"). `name` is the human display name. Defaults: `isPublic: true` (INTERNAL visibility — all workspace members can view), `isEditPublic: false`. NOTE: `isPublic` is internal workspace visibility ONLY; it does NOT publish the space to the public web — use wiki_set_public_settings for that. Requires workspace-level edit access. API-key scope: `wiki:spaces:write`.
wiki_update_spaceUpdate a wiki space's metadata. All fields are optional — pass only what you want to change. The space key cannot be changed. Requires edit access to the space. API-key scope: `wiki:spaces:write`.
wiki_delete_spacePERMANENTLY delete a wiki space AND every page inside it. Requires admin access to the space. This is destructive — surface a clear confirmation to the user before calling. Returns 204. API-key scope: `wiki:spaces:write`.
wiki_get_public_settingsGet a space's PUBLIC-WEB publishing settings (PublicSpaceSettingsDTO): `isEnabled` (is the space published to the public internet), `customSlug` (public URL slug), `allowedEmojis`, `showReactions`, `showPageViews`, `showLastUpdated`, `showAuthor`, `viewMode` ("space"|"helpcenter"), `heroTitle`, `heroSubtitle`. This is SEPARATE from the space's `isPublic` flag, which is internal workspace visibility only. Requires space admin. API-key scope: `wiki:spaces:read`.
wiki_check_public_slugCheck whether a public URL slug is available and validly formatted for a space, before publishing. Returns a SlugAvailabilityDTO. Call this when choosing a `customSlug` for wiki_set_public_settings. Requires space admin. API-key scope: `wiki:spaces:read`.
wiki_set_public_settingsPublish / unpublish a space to the PUBLIC INTERNET, or update its public-site config. This is the REAL publish switch — NOT the space `isPublic` flag (which is internal visibility). Pass only the fields you want to change: `isEnabled` (true = publish to the web, false = take offline), `customSlug` (public URL slug — validate first with wiki_check_public_slug), `allowedEmojis` (string[]), `showReactions`, `showPageViews`, `showLastUpdated`, `showAuthor`, `viewMode` ("space"|"helpcenter"), `heroTitle`, `heroSubtitle`. Provided fields are merged onto the current settings (read-modify-write), so unspecified fields are preserved. Minimal publish: { isEnabled: true, customSlug: "my-docs" }. ⚠️ HIGH-TRUST / OUTWARD-FACING: enabling makes the space readable by ANYONE on the internet — confirm with the user before publishing. Requires space ADMIN. API-key scope: `wiki:spaces:write`.
wiki_list_attachmentsList every attachment on a wiki page (WikiAttachmentDTO[]): id, pageId, filename, contentType, sizeBytes, status (pending|confirmed|failed), uploadedBy/At, confirmedAt. `pageId` is the page UUID (from wiki_get_space_with_pages tree node `id`, not the slug). Use to find an attachmentId to reference or delete. API-key scope: `wiki:attachments:read`.
wiki_request_attachment_uploadStep 1 of uploading an image/file to a wiki page. Returns { attachmentId, uploadUrl, storageKey }. AFTER calling this you MUST: (2) PUT the raw file bytes to `uploadUrl` with your OWN HTTP client — the MCP server cannot do this binary upload — sending the EXACT same `Content-Type` as `contentType` and a `Content-Length` equal to `sizeBytes` (both are baked into the presigned URL; a mismatch 403s); then (3) call wiki_confirm_attachment to activate it. To embed the result as an image, add a TipTap image node with no `src` — { type:"image", attrs:{ attachmentId, pageId, width, height, align } }, width <= ~660 and height proportional — via wiki_update_page (content payload). Do NOT embed base64 data: URIs; they render distorted. Max 25 MB; system-executable file types are rejected. `pageId` is the page UUID (wiki_get_space_with_pages tree node `id`). API-key scope: `wiki:attachments:write`.
wiki_confirm_attachmentStep 3 of uploading: confirm that the bytes were successfully PUT to the presigned `uploadUrl`, activating the attachment. Returns the WikiAttachmentDTO (status becomes "confirmed"). Call only after the byte PUT succeeded. API-key scope: `wiki:attachments:write`.
wiki_delete_attachmentPermanently delete an attachment and its stored file (returns 204). Useful for cleaning up unused or leftover uploads. This does not remove image nodes that still reference it in a page body — update the page content separately if needed. API-key scope: `wiki:attachments:write`.
fr_list_requestsList feature requests on a feedback board (by board slug). Filter by status / category / milestone name (lenient — trimmed + case-insensitive). Pass `q` to search request titles instead. Paginated via page/size. API-key scope: `feedback:requests:read`.
fr_get_requestGet a feature request by short ID (e.g. "FR-42"). Returns full detail: title, description, status, category, milestone, voteCount, commentCount, reactions. Internal notes and linkedTaskIds are populated only when the caller has `View Internal Data` permission. API-key scope: `feedback:requests:read`.
fr_create_requestCreate a new feature request on a board. Category is resolved by name (lenient match). No turnstile token required — API-key authentication is sufficient. Returns the new request with assigned shortId. API-key scope: `feedback:requests:write`.
fr_set_request_statusChange a feature request's status by name. The name is resolved leniently against the request's board's status set (trim + case-insensitive). Returns the updated request detail. API-key scope: `feedback:requests:write`.
fr_comment_requestAdd a comment to a feature request. Pass isInternal=true to make the comment visible only to users with `View Internal Data` permission. API-key scope: `feedback:comments:write`.
fr_vote_requestToggle a vote or emoji reaction on a feature request. Passing emoji=null or omitting the field registers a plain upvote. Calling the tool again with the same emoji removes the vote (idempotent toggle). API-key scope: `feedback:votes:write`.
fr_moderate_requestApprove, reject, or mark a feature request as spam. Action is case-insensitive. Requires `Manage Queue` permission. API-key scope: `feedback:moderation:write`.
fr_delete_requestPermanently delete a feature request. Requires `Manage Queue` permission. Returns 204 on success. This operation is irreversible — confirm with the user before calling unless the intent is unambiguous. API-key scope: `feedback:requests:write`.
fr_list_bugsList bug reports on a feedback board (by board slug). Filter by severity and/or status name (lenient match). API-key scope: `feedback:bugs:read`.
fr_get_bugGet a bug report by short ID (e.g. "BG-99"). Returns full detail: title, reproduction steps, expected/actual result, severity, status, product area, assignee, affectedCount, environment, comments count. Internal notes and linkedIssueUrl populated only for `View Internal Data` permission. API-key scope: `feedback:bugs:read`.
fr_create_bugCreate a new bug report on a board. Severity and productArea are resolved by name (lenient match). Environment is a free-form map (browser, OS, url, etc.). API-key scope: `feedback:bugs:write`.
fr_set_bug_statusChange a bug status by name (lenient match against the board's bug-status set). API-key scope: `feedback:bugs:write`.
fr_set_bug_assigneeAssign or unassign a bug. Provide `assigneeEmail` (resolved case-insensitive against workspace members) OR `assigneeId` (UUID). Exactly one; both = 400. Passing neither unassigns. API-key scope: `feedback:bugs:write`.
fr_set_bug_visibilityToggle a bug's public visibility. Security bugs stay private regardless. API-key scope: `feedback:bugs:write`.
fr_toggle_bug_affectedToggle the caller's "I'm affected" marker on a bug. Returns the updated bug detail with new affectedCount. API-key scope: `feedback:bugs:write`.
fr_comment_bugAdd a comment to a bug report. Pass isInternal=true for internal-only. API-key scope: `feedback:comments:write`.
fr_moderate_bugApprove, reject, or mark a bug as spam. Action is case-insensitive. Requires `Manage Queue` permission. API-key scope: `feedback:moderation:write`.
fr_delete_bugPermanently delete a bug report. Requires `Manage Queue` permission. Irreversible. API-key scope: `feedback:bugs:write`.
pm_get_workspace_contextSingle-call workspace orientation: members, spaces (with folders, lists, per-list statuses/priorities/taskTypes/customFields), workspace-level taskTypes, relationshipTypes, tags. The biggest agent-onboarding tool — call it first when starting in a new workspace. Pass shallow=true to skip per-list statuses/priorities for a faster tree-only response. Each per-list custom field carries an `isMandatory` flag — fields with isMandatory=true MUST be supplied in `customFields` when creating/updating a task in that list, or the write is rejected with 400 VALIDATION_ERROR. API-key scope: `workspaces:read`.
pm_get_dashboardGet aggregated counts and breakdowns (status / priority / assignee distributions, custom-field summaries) for any scope. Useful for "how is project X doing?" questions without paginating through tasks. API-key scope: `dashboards:read`.
pm_search_tasksSearch tasks across the workspace with name-based filters. status / priority / tag / taskType are repeatable (pass an array). assignee is an email or UUID. q is a free-text search over title + description. Returns a cursor-paginated page of LiteTaskResponse — pass nextCursor back as `cursor` to paginate. Present title linked to webUrl; show displayKey only when non-empty. key and identifier are API references, not display labels. API-key scope: `tasks:read`.
pm_get_taskFetch a task by ref. Ref accepts a system identifier (tsk_…) OR a task key (e.g. 'PROJ-42'). Returns LiteTaskResponse with names instead of UUIDs and emails instead of user UUIDs. Internal note: when ref is a task key the workspace query param is required — the MCP injects it automatically. Present title linked to webUrl; show displayKey only when non-empty. Do not display the raw key when displayKey is null or absent. API-key scope: `tasks:read`.
pm_get_subtasksList the direct subtasks (one level deep) of a parent task by ref. API-key scope: `tasks:read`.
pm_create_taskCreate a task. In the result, title/webUrl are for presentation; displayKey is the optional visible key. Keep key/identifier for API calls and do not expose a hidden raw key in the summary. References are name-based: status/priority/level/taskType are names; assignees are emails; tags are strings (auto-created if missing); customFields is a {name: value} map. `list` is the task-list identifier (tl_…). For subtasks, set `parent` to a task key or identifier (omit `list` and the parent's list is used). Task type is OPTIONAL: omit `taskType` to inherit the closest non-null default along the three-level chain `list → folder → space`. There's NO workspace-level fallback — if all three are null the task is created untyped (`taskType: null` in the response), which is a valid persistent state. Use `pm_list_task_types` to see what types this workspace has (9 SYSTEM rows seeded at workspace creation, plus any CUSTOM ones). MANDATORY CUSTOM FIELDS: a list can mark custom fields required (isMandatory, per field via pm_get_workspace_context). Populate them in `customFields` on create AND update — the API rejects a write that leaves one empty with HTTP 400 errorCode VALIDATION_ERROR, details.field = the field's display name; the message also names it (e.g. Mandatory custom field 'Priority' requires a value). Fix and retry; don't ask the user as a substitute. API-key scope: `tasks:write`.
pm_update_taskPartial-update a task by ref. Only fields present in the call are changed. Pass an explicit null to clear nullable fields (dueDate, parent, taskType, etc.). Names resolve leniently against the current effective set. To change just the type and nothing else, prefer this with `taskType` set; use `pm_bulk_change_task_type` when changing many tasks at once. API-key scope: `tasks:write`.
pm_delete_taskDelete a task by ref. Cascade-deletes subtasks. Requires FULL access (not just EDIT). Returns 204 on success. API-key scope: `tasks:write`.
pm_list_task_typesReturn the workspace task-type catalogue (identifier, name, singularName, pluralName, iconKind, iconValue, color, sortOrder, origin SYSTEM/CUSTOM). Use this to discover what types are available before creating/updating tasks, or to translate names to stable identifiers for the cascade-default endpoints. API-key scope: `workspaces:read`.
pm_bulk_change_task_typeChange the task type for many tasks at once (≤5000 per call). `taskIdentifiers` are stable wire identifiers (e.g. tsk_…) — task keys (PROJ-42) are NOT accepted here; use pm_search_tasks first if you only have keys. `taskType` is a name (e.g. "Bug") or null to clear the type. Returns 200 sync for ≤500 tasks; 202 with a {jobId, statusUrl} for larger batches — poll the statusUrl for completion. API-key scope: `tasks:write`.
pm_list_task_commentsList comments on a task by ref. Cursor-paginated. API-key scope: `tasks:read`.
pm_create_task_commentAdd a comment to a task. `mentions` is an array of emails — the server resolves them to user UUIDs and substitutes `@<email>` literals in `text` with mention spans. Pass `replyTo` (a comment identifier) to thread. API-key scope: `tasks:write`.
pm_update_task_commentUpdate an existing comment. Only the original author may edit. API-key scope: `tasks:write`.
pm_delete_task_commentDelete a comment. Only the original author may delete. Returns 204. API-key scope: `tasks:write`.
pm_list_task_relationshipsList all relationships where the task is owner OR child. Cursor-paginated. API-key scope: `tasks:read`.
pm_create_task_relationshipCreate a relationship from one task to another. `type` is the relationship-type name in the workspace (e.g. "Blocking"). `target` is a task key or identifier. The current task (ref) is the owner. API-key scope: `tasks:write`.
pm_delete_task_relationshipDelete a relationship by identifier. Returns 204. API-key scope: `tasks:write`.
pm_create_spaceCreate a new space in the current workspace. Description / icon / color / isPrivate are optional metadata. Returns LiteSpaceResponse. API-key scope: `spaces:write`.
pm_create_folderCreate a folder inside a space. Space identified by name. API-key scope: `folders:write`.
pm_update_folderUpdate folder metadata by identifier (fld_…). All fields optional. API-key scope: `folders:write`.
pm_delete_folderSoft-delete a folder and its child lists+tasks. Requires FULL access. 204. API-key scope: `folders:write`.
pm_create_listCreate a task list inside a space (optionally inside a folder). Space and folder are identified by name. Omit folder to create the list directly under the space. Prefer setting icon and color on create when the list purpose is known. For icon, prefer a semantic emoji name first; use an icon identifier only when no emoji fits. API-key scope: `lists:write`.
pm_update_listUpdate list metadata by identifier (tl_…). All fields optional. API-key scope: `lists:write`.
pm_delete_listSoft-delete a list and its tasks. Requires FULL access. 204. API-key scope: `lists:write`.
pm_create_custom_fieldCreate a custom field at workspace / space / list scope. scope=workspace ignores scopeName; scope=space takes a space name; scope=list takes a list name (first match in the workspace). For dropdown / labels (multi-select) types, pass `options` as an array of {value, color?, emoji?, orderIndex?}. Keep field names plain for column headers; use emoji/color metadata for visual icons. CREATING A FIELD IS NOT ENOUGH TO MAKE IT VISIBLE: a custom field only shows up where it's added to a view's columns. After creating fields for a list, finish by creating/updating a view (pm_create_view / pm_update_view) whose `columns` include these fields, or the list keeps a defaults-only, empty-looking view. API-key scope: `custom_fields:write`.
pm_update_custom_fieldUpdate custom-field metadata (name / description / emoji / color / isPrivate). API-key scope: `custom_fields:write`.
pm_delete_custom_fieldDelete a custom field and all its values. Requires FULL access. 204. API-key scope: `custom_fields:write`.
pm_list_viewsList views at a given scope. scope is one of workspace/space/folder/list; scopeIdentifier is the UUID of the parent entity (omit for workspace scope — the MCP's configured workspace is used). Cursor-paginated. API-key scope: `views:read`.
pm_get_viewFetch a view by identifier (vw_…). API-key scope: `views:read`.
pm_create_viewCreate a view. type is one of list / board / table / dashboard / gantt / calendar / gallery. ALWAYS pass `columns` listing exactly what should be visible, in display order, INCLUDING every custom field you want shown — a view created without `columns` falls back to system defaults, so custom fields you just created will NOT appear and the view looks empty. This is the most common mistake here: do not create a view and forget to select its columns. If unsure which custom-field column identifiers exist for this scope, call pm_get_workspace_context (or pm_list_views) first instead of guessing. Columns and filters are applied atomically with the create — invalid columnIdentifier or filter shape rolls the whole create back with 400, so a 201 always means the view exists and is fully configured. In columns, the list order is display order and omitted columns are hidden. Keep new custom-field/header names plain; custom-field icons belong in emoji/color metadata. API-key scope: `views:write`.
pm_update_viewUpdate view metadata. filters / columns are pass-through to the existing FilterGroupDTO / ColumnOrderItem shapes. API-key scope: `views:write`.
pm_delete_viewDelete a view by identifier. Mandatory views (system-created defaults) return 409 Conflict. Returns 204 on success. API-key scope: `views:write`.
pm_clone_viewClone an existing view into a (possibly different) scope. Requires VIEW on the source and EDIT on the target scope. API-key scope: `views:write`.
pm_list_sprint_groupsList all sprint groups in a space. Sprint groups are containers for sprints — each group has its own state machine (only one IN_PROGRESS sprint per group). Returns an array of SprintGroupDTO. API-key scope: `sprints:read`.
pm_create_sprint_groupCreate a sprint group inside a space. `name` is required (max 100 chars). `description` is optional (max 2000 chars). `defaultDurationDays` is the default sprint length used when creating new sprints (1–90 days, optional). API-key scope: `sprints:write`.
pm_create_sprintCreate a sprint inside a sprint group. New sprints start in NOT_STARTED state. `name` required (max 200 chars). `goal`, `startDate`, `endDate` optional (ISO-8601 instants for dates). API-key scope: `sprints:write`.
pm_get_sprintFetch a sprint by identifier. Returns SprintDTO with task statistics. API-key scope: `sprints:read`.
pm_update_sprintFull update of sprint name, goal, and date window. NOTE: this is a PUT, not a PATCH — fields you omit may be cleared by the backend. Pass every field you want to keep. API-key scope: `sprints:write`.
pm_delete_sprintSoft-delete a sprint. Tasks lose their sprint association but remain in their lists. 204 on success. API-key scope: `sprints:write`.
pm_start_sprintTransition a sprint from NOT_STARTED to IN_PROGRESS. Only ONE sprint per group can be IN_PROGRESS at a time — starting a sprint while another is in progress will fail. No body. API-key scope: `sprints:write`.
pm_complete_sprintTransition a sprint from IN_PROGRESS to DONE. Optionally pass `rolloverSprintIdentifier` to move incomplete tasks into a different sprint (typically the next one in the group). Omit the field to leave incomplete tasks unsorted (no rollover). API-key scope: `sprints:write`.
pm_add_tasks_to_sprintAssociate tasks with a sprint. All tasks must belong to the same space as the sprint group. Pass identifiers (tsk_…), not task keys. Returns updated SprintDTO. API-key scope: `sprints:write`.
pm_remove_tasks_from_sprintRemove task-sprint associations. Tasks remain in their lists. Pass identifiers (tsk_…), not task keys. Returns updated SprintDTO. API-key scope: `sprints:write`.
pm_get_sprint_tasksList all tasks currently in the sprint. Returns an array of full TaskDTO. API-key scope: `sprints:read`.
pm_get_sprint_burndownReturn burndown/burnup chart data for the sprint — daily snapshots of remaining vs completed work. Use this to render burndown charts or audit sprint progress over time. API-key scope: `sprints:read`.
pm_create_webhookCreate an outgoing webhook subscription for the current workspace. The response includes a one-time `secret` (HMAC-SHA256 key used to verify the X-Webhook-Signature-256 header on delivery). SAVE THIS SECRET IMMEDIATELY — subsequent reads (pm_get_webhook / pm_list_webhooks) do NOT return it; the only way to get a new one is to delete and recreate the webhook. eventTypes are dash-cased names (e.g. "task-created", "task-status-changed", "comment-added"); the catalog has 130+ entries — common ones include task-created/deleted, task-status-changed, task-priority-changed, task-assignee-added/removed, task-due-date-updated, comment-added/updated, reaction-added, custom-field-value-updated, space-deleted, folder-deleted, task-list-deleted, workspace-user-role-changed. Optionally narrow delivery to a single entity by setting scopeType (SPACE / FOLDER / TASK_LIST / TASK) plus scopeEntityIdentifier; omit both for workspace-wide delivery. Outgoing payload envelope is {version, id, type, timestamp, workspaceIdentifier, data}; retries fire at +0s / +1min / +5min (3 attempts total) and treat both 4xx and 5xx as failures. API-key scope: `webhooks:write`.
pm_list_webhooksList all webhook subscriptions registered in the current workspace. The HMAC `secret` is NOT included — only present in the original create response. API-key scope: `webhooks:read`.
pm_get_webhook_usageReport webhook quota for the current workspace: { userManaged, agentManaged, total, max }. `total` is the count of active subscriptions and `max` is the per-workspace cap; `agentManaged` is the subset created via API keys (like this MCP). Check this before calling pm_create_webhook in bulk — creation fails once `total` reaches `max`. API-key scope: `webhooks:read`.
pm_get_webhookFetch a single webhook by identifier. Returns its url / name / eventTypes / scope / active flag; does NOT return the HMAC secret (only available at creation time). API-key scope: `webhooks:read`.
pm_update_webhookPartial-update a webhook subscription. Only fields present in the call are changed (pass-through PATCH-style semantics). Use `active: false` to pause deliveries without deleting. Updating eventTypes replaces the full subscribed set. Does not return or rotate the HMAC secret. API-key scope: `webhooks:write`.
pm_delete_webhookDelete a webhook subscription permanently. Stops all future deliveries. Returns 204. The HMAC secret cannot be recovered — recreate the webhook to get a new one. API-key scope: `webhooks:write`.
pm_test_webhookFire a synthetic test delivery to a webhook on demand, without waiting for a real workspace event. PM POSTs a `webhook-test` event with body {"test": true, "message": "This is a test webhook delivery"} to the registered URL, signed with the same X-Webhook-Signature-256 HMAC as live deliveries. Use this to verify a receiver is reachable and that your HMAC signature-verification is correct when setting up two-way communication. Returns the resulting delivery record (status, attempt, timestamps) — inspect it (or pm_list_webhook_deliveries) to confirm the endpoint accepted it. API-key scope: `webhooks:write`.
pm_list_webhook_deliveriesList recent delivery attempts for a webhook (most recent first). Each entry includes the event type, response status, attempt count, and timestamps. Useful for diagnosing why a subscriber is missing events. Pagination uses `cursor` (or `page`) and `size` (max 100, default backend-defined). API-key scope: `webhooks:read`.
pm_replay_webhook_deliveryRe-send a specific past delivery to the webhook URL. Useful when the subscriber was down during the original attempt window or you need to re-trigger downstream processing. Replays use the same payload, signature, and X-Webhook-Delivery id as the original — subscribers MUST treat receipt of a duplicate delivery id as idempotent. API-key scope: `webhooks:write`.
pm_read_activity_logRead the activity log for a scope. `scope` selects the entity type and `identifier` is that entity's identifier (use the workspace identifier when scope=workspace). `mode` is either 'full' (this entity AND everything beneath it) or 'own' (this entity only). Cursor-paginated. WARNING: every entry has a `data` field that is a JSON-encoded STRING — to inspect the payload you must double-parse it (parse the response, then JSON.parse(entry.data)). API-key scope: `activity_log:read`.
pm_list_notificationsList notifications for the current user in the active workspace. NOTE: this endpoint uses PAGE-style pagination (?page=&size=) not cursor-based — unusual for this API. `page` is 0-indexed; `size` is 1–100. Optional `unreadOnly`, `sortColumn`, `sortDirection`. API-key scope: `notifications:read`.
pm_count_unread_notificationsReturn the bare unread-notification count (a Long) for the current user in the active workspace. The response body is a single number, not an object. API-key scope: `notifications:read`.
pm_mark_notification_readMark a single notification as read. Only the notification owner may do this — calling with another user's notification identifier returns an error. API-key scope: `notifications:write`.
pm_mark_all_notifications_readMark every unread notification in the active workspace as read for the current user. API-key scope: `notifications:write`.
pm_list_time_entriesList time entries logged against a task. `taskIdentifier` must be a stable identifier (tsk_…), not a task key. Supports page/size/sortColumn/sortDirection (page-style). API-key scope: `time:read`.
pm_log_timeLog a time entry against a task. `timeSpent` is in minutes (0 to 10080 — 7 days max). `startedAt` is an ISO-8601 instant marking when the tracked work started. `notes` is optional (max 10000 chars). The user is set server-side from the JWT — do NOT pass userUuid. API-key scope: `time:write`.
pm_delete_time_entryDelete a time entry from a task. NOTE: `timeEntryId` is a numeric Long (e.g. 42), NOT a slug/identifier. Returns 204 on success. API-key scope: `time:write`.
pm_list_saved_filtersList the current user's saved filters for a list. Filters are USER-scoped — they are not visible to other workspace members. API-key scope: `filters:read`.
pm_save_filterCreate a new saved filter on a list. Body is a FilterAggregateDTO with structured `filterGroups` — each group has a `precedingLogic` (AND/OR) and a list of filters. Each filter has `field`, `operator` (one of: is, equals, not, not_equals, like, greater_than, less_than, greater_or_equal, less_or_equal, is_set, is_not_set, in, not_in), `value`, optional `precedingLogic`, and `isCustomField` flag. Max 10 groups, max 20 filters per group. No PATCH/PUT exists — to edit, delete + re-create. API-key scope: `filters:write`.
pm_delete_saved_filterDelete a saved filter you own. NOTE: `id` is a numeric Long (e.g. 42), NOT a slug. Only the owner may delete. Returns 204. There is NO endpoint to "apply" a saved filter — that is a UI affordance only. API-key scope: `filters:write`.
pm_add_comment_reactionAdd an emoji reaction to a task comment. `reactionType` is the emoji code (e.g. "thumbs_up", "heart", "smile"). Each user may add at most one reaction of each reactionType per comment. Requires COMMENT-level access on the task. API-key scope: `tasks:write`.
pm_list_comment_reactionsList reactions on a task comment. Page-style pagination (page/size). API-key scope: `tasks:read`.
pm_remove_comment_reactionRemove a reaction by identifier. Only the user who added the reaction may remove it. 204. API-key scope: `tasks:write`.
pm_list_reference_dataList a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.
pm_get_task_sharingRead a task's current public sharing settings. Returns the full TaskSharingSettingsDTO — `shared` (is the public link active), `publicLink` (the share URL when active), `expiresAt`, and per-field visibility toggles (shareAssignee, shareDescription, shareStatus, sharePriority, shareDueDate, shareComments, shareAttachments, shareCustomFields, shareSubtasks, shareTags) plus the explicit list of custom-field identifiers exposed (sharedCustomFieldIdentifiers). Requires at least VIEW access to the task. API-key scope: `tasks:read`.
pm_configure_task_sharingEnable, disable, or reconfigure public sharing for a task. Pass `shared: true` to generate a public link (or refresh the configuration); the response includes the resulting publicLink. Pass `shared: false` to revoke an existing share. All other fields are optional toggles for which slices of the task are visible to a public viewer. Requires FULL access to the task. API-key scope: `tasks:write`.
pm_create_tagCreate a new tag in a space. Tags are auto-created on first inline use (e.g. `tags: ["urgent"]` when creating a task via the Lite API), so use this only when you need to pre-create a tag with specific colors before applying it. Returns the persisted TagDTO with its identifier. API-key scope: `tags:write`.
pm_get_tagFetch a single tag by identifier. Returns the TagDTO (identifier, name, backgroundColor, textColor). API-key scope: `tags:read`.
pm_update_tagRename or recolor an existing tag. All updatable fields are optional — pass only what you want to change. The tag identifier stays the same; any task already tagged keeps the new name and colors automatically. API-key scope: `tags:write`.
pm_delete_tagDelete a tag. The tag is removed from every task that currently carries it; the tasks themselves are not affected. Returns 204. API-key scope: `tags:write`.
pm_list_teamsList teams in the current workspace, paginated. Each team carries identifier, name, alias, description, icon, color, and member list. Use pagination if there are many teams. API-key scope: `teams:read`.
pm_create_teamCreate a new team in the current workspace. Returns the persisted TeamDTO including its identifier. Requires the workspace MANAGE_TEAMS permission. API-key scope: `teams:write`.
pm_get_teamFetch a team by identifier. Returns the full TeamDTO with members. API-key scope: `teams:read`.
pm_update_teamUpdate a team's metadata or replace its full member list. All fields are optional — only specified fields change. NOTE: `memberUuids`, if present, REPLACES the existing membership (not appends). Use pm_add_team_member / pm_remove_team_member for incremental changes. Requires the workspace MANAGE_TEAMS permission. API-key scope: `teams:write`.
pm_delete_teamDelete a team. Removes the team and all of its grants — existing access controls that referenced this team are reduced accordingly. Returns 204. Requires the workspace MANAGE_TEAMS permission. API-key scope: `teams:write`.
pm_add_team_memberAdd a single user to a team. Pass the user UUID (from pm_list_workspace_members). Idempotent — adding a user who is already a member is a no-op. Requires MANAGE_TEAMS. API-key scope: `teams:write`.
pm_remove_team_memberRemove a single user from a team. Returns 204. Requires MANAGE_TEAMS. API-key scope: `teams:write`.
pm_get_current_userGet the profile of the human behind the API key — identifier, email, fullName, and the userSettings object. Use this when the agent needs to address the user by name, route a notification to the right preference channel, or confirm "whose API key am I holding". API-key scope: `users:read`.
pm_update_current_userUpdate the current user's profile. Today the request body has a single field (`fullName`) — pass the new display name. Returns the updated TaskManagementUserDTO. API-key scope: `users:write`.
pm_get_notification_settingsRead the current user's aggregated notification settings — one tree covering every module (comments, mentions, assignments, due dates, automation events, …) and every delivery channel (app / browser / email). Use this to find out which channel is on for a given event before asking the user to flip a flag. API-key scope: `users:read`.
pm_update_notification_channelEnable or disable a single notification module/channel combination — e.g. email-off for due-date reminders. The module names come from pm_get_notification_settings. Pass `enabled: true|false`. To bulk-toggle all channels for a module, repeat this tool for each channel; there is no bulk endpoint. API-key scope: `users:write`.
pm_get_workspace_user_avatar_urlReturn the avatar URL for a specific user in the current workspace. The response is a short-lived signed URL pointing at the user's avatar image — embed it in chat messages, mentions, or attribution UI. Returns null if the user has no avatar set. API-key scope: `users:read`.
pm_list_automations_for_listList automations scoped to a specific list. Each row is an AutomationDTO with name, active, triggers, conditionNodes, actions, and the owning scope identifiers. API-key scope: `automations:read`.
pm_list_automations_for_folderList automations scoped to a folder. Automations attached at folder level cascade to every list inside that folder unless overridden at the list level. API-key scope: `automations:read`.
pm_list_automations_for_spaceList automations scoped to a space. Automations attached at space level cascade to every list and folder inside that space. API-key scope: `automations:read`.
pm_get_automationFetch a single automation by identifier. Returns the full AutomationDTO including triggers, condition tree, and actions. API-key scope: `automations:read`.
pm_create_automationCreate an automation rule. Exactly ONE scope must be set — `listIdentifier` OR `folderIdentifier` OR `spaceIdentifier`. `triggers` and `actions` are arrays; `conditionNodes` is the flattened condition tree (omit for "always-true"). All `parameters` fields on triggers/actions/conditions are JSON-encoded strings, not nested objects. Before crafting, call pm_list_reference_data to learn the valid action/condition/trigger types. API-key scope: `automations:write`.
pm_update_automationUpdate an existing automation. All fields except `identifier` are optional — only specified fields change. `triggers`, `actions`, and `conditionNodes`, when present, REPLACE the existing collection (not append). Use `active: false` to disable without deleting. API-key scope: `automations:write`.
pm_delete_automationDelete an automation rule. Returns 204. Existing audit log rows are preserved. API-key scope: `automations:write`.
pm_get_automation_auditFetch the execution audit log for an automation. Each row records a single firing — timestamp, triggering task, trigger type, overall execution status (SUCCESS/FAILED/IN_PROGRESS/ROLLED_BACK), and per-action audit detail. Use to debug "did my automation run?" — it is the authoritative answer; the UI does not currently show summary stats. API-key scope: `automations:read`.
pm_list_workspace_membersList members of the current workspace. Workspace is taken from the MCP config — no need to pass it. RESPONSE IS A PAGINATED ENVELOPE, NOT AN ARRAY: {users: WorkspaceUserDTO[], totalCount, page, size, totalPages} — read members from `users` (treating the response itself as a list fails). FOOTGUN: `size` DEFAULTS TO 20 when omitted, so a single call silently returns only the first 20 members and no error — don't assume it's the full roster. To enumerate everyone, page (page is 0-based) until you have collected `totalCount`. `size` is capped at 100 and a value >100 is a 400, not clamped. Use `search` (case-insensitive substring on first/last name or email, applied before paging) to find a specific member instead of paging blindly. Side effect: updates the caller's last-active timestamp. API-key scope: `workspaces:read`.
pm_change_member_roleChange a member's workspace access level. `userUuid` is the target user's UUID (NOT email — call pm_list_workspace_members first to find it). `workspaceAccessLevelId` is a numeric Long id from the workspace `/access-levels` catalogue (e.g. 1, 2, 3) — fetch it via the catalog meta tools or your existing endpoint introspection if you don't already have it. Caller needs MANAGE_USERS permission. Note: this endpoint is HTTP PUT on the collection path (not PATCH on a sub-resource). API-key scope: `workspaces:write`.
pm_remove_workspace_memberRemove a member from the workspace. NOTE: the target user UUID is passed as the `deletionUserUuid` QUERY parameter, not in the path or body. Caller needs MANAGE_USERS permission. Cannot remove the workspace owner — transfer ownership first via pm_transfer_workspace_ownership. Returns 204. API-key scope: `workspaces:write`.
pm_transfer_workspace_ownershipTransfer workspace ownership to another existing member. Only the current owner can do this, and the target user must already be a member. `resultingOwnerAccessLevelId` is the numeric access-level id the CURRENT (departing) owner will keep — typically a regular admin/member level. Discover access-level ids via /v1/workspaces/{ws}/access-levels. API-key scope: `workspaces:write`.
pm_leave_workspaceVoluntarily leave the current workspace. WARNING: this affects the calling user (the user identity behind the API key) — there is no parameter to pick a different user. The workspace owner cannot leave; they must transfer ownership first. After a successful leave the API key may stop working against this workspace. No body. API-key scope: `workspaces:write`.
pm_list_invitationsList pending (not yet accepted, not expired) invitations for the current workspace. Caller needs MANAGE_USERS permission. Returns an array of InvitationDTO. API-key scope: `users:read`.
pm_send_invitationSend an email invitation to join the current workspace. `workspaceAccessLevelId` is a numeric Long id (NOT a name like "admin"/"member") — fetch the catalogue from /v1/workspaces/{ws}/access-levels to translate role names to ids before calling. Caller needs MANAGE_USERS permission. Returns 201 on success. API-key scope: `users:write`.
pm_cancel_invitationRevoke a pending workspace invitation by its identifier. Caller needs MANAGE_USERS permission. Returns 204. API-key scope: `users:write`.
pm_list_import_jobsList CSV import jobs for the current workspace, paginated. The actual CSV upload endpoints (/csv and /csv/preview) are multipart/form-data and are not exposed by the MCP — agents that want to start a fresh import must upload via a non-MCP client and then come back here with the returned jobIdentifier. API-key scope: `imports:write`.
pm_get_import_jobFetch the current status and progress of a CSV import job by identifier. Use this to poll a job that another client started via /csv or /csv/preview. API-key scope: `imports:write`.
pm_confirm_import_mappingsConfirm column mappings for a previewed CSV import job and start async import processing. Call this AFTER another (non-MCP) client has uploaded the CSV via /csv/preview and produced a job in PREVIEW status. `columnMappings` is a non-empty array of objects with: csvHeader (exact CSV column name), targetField (e.g. 'title', 'status', or a custom field identifier), and targetType ('builtin' or 'custom_field'). API-key scope: `imports:write`.
pm_describe_status_priority_level_endpointsOrientation/meta tool: return the canonical REST paths and field shapes for managing the Status, Priority, and Task-Level catalogues at each scope (workspace / space / folder / list). Call this ONCE before reaching for endpoint-example tools — it cuts a 30-tool surface down to a single readable map. The agent can then use the catalog tools (e.g. `get_endpoint_examples`) to fetch real request/response bodies for whichever path it picks.
纠错与举报（发现条目失效、署名有误或涉及侵权？）
提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。