Kanera

Name: Kanera
Author: kanera

Connect AI assistants to Kanera project management. Search and manage work across boards and workspaces, including cards, assignments, due dates, checklists, comments, attachments, personal notes, priorities, automations, activity history, reporting, and portfolio insights. Kanera MCP also supports creating new workspaces and boards from templates.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://kaneramcp--kanera.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "Kanera": {
      "url": "https://kaneramcp--kanera.run.tools"
    }
  }
}

能力清单

工具	说明
session.get	Describe the current Kanera credential and canonical web URL. Personal OAuth/API credentials are identity-wide across the user's live organisation memberships; service/workspace credentials report their pinned workspace.
workspaces.list	List a cursor-paginated directory of accessible standard workspaces. Standalone boards and parent workspaces reached only through board-level guest access are excluded; use boards.list_accessible for complete board discovery.
boards.list_accessible	Discover a cursor-paginated directory of every accessible workspace board, standalone board, and cross-organisation guest board.
workspaces.list_templates	List the built-in workspace templates with the lists, custom fields, labels, and seed-content counts each one provides. Call before workspaces.create or boards.create_standalone to choose a templateId; "blank" seeds nothing.
workspaces.create	Create a standard workspace whose lists, custom fields, and labels are shared by every board inside it, optionally with an initial board. Choose a templateId from workspaces.list_templates, or supply explicit lists/customFields/labels (they replace the template's; template starter cards and automations that depend on removed items are skipped). Omitting both applies Kanera's default lists, fields, and labels. Requires an organisation admin or owner using a write-capable personal API key or an interactive OAuth grant; workspace-scoped and read-only credentials receive 403 FORBIDDEN. Check session.get: credentialKind must not be "workspace" and scope must not be "read". This is not idempotent; do not retry after an ambiguous success.
boards.create_standalone	Create a standalone board with its own private lists, custom fields, and labels (no visible workspace). Defaults to the "development-team" template; pass templateId "blank" or explicit lists for a minimal board. The board is hidden from workspaces.list and visible in boards.list_accessible; read its configuration with boards.get_standalone_settings. Requires an organisation admin or owner using a write-capable personal API key or an interactive OAuth grant; workspace-scoped and read-only credentials receive 403 FORBIDDEN. Check session.get: credentialKind must not be "workspace" and scope must not be "read". This is not idempotent; do not retry after an ambiguous success.
boards.create	Add a board to an existing standard workspace. The new board shares the workspace's lists, custom fields, labels, and automations. Requires workspace-admin authority and a write-capable credential (workspace-scoped admin keys work here, unlike workspaces.create). Standalone boards cannot receive a second board; use boards.create_standalone instead. This is not idempotent; do not retry after an ambiguous success.
workspaces.get	Read a standard workspace and its shared lists, custom fields, labels, templates, and automations. For a standalone board, use boards.get_standalone_settings.
automations.list	List the ordered automation rules and lifetime run statistics for a standard workspace. Requires workspace-admin authority; use workspaces.get when only general readable workspace configuration is needed.
automations.list_executions	List a cursor-paginated history of one automation's retained execution outcomes (effectful, no-op, or failed), newest first. Requires workspace-admin authority.
automations.create	Create a workspace automation with an ordered action list. Requires workspace-admin authority and a write-capable credential. For a rule that runs only when a card moves into a list, use card_enters_list with applyOnCreate=false and applyOnMove=true; add_assignees plus set_due_date implements a review handoff with a relative deadline. This is not idempotent; do not retry after an ambiguous success.
automations.update	Atomically update an automation's trigger settings and/or replace its full ordered action list. Requires workspace-admin authority and a write-capable credential. Use automations.set_enabled for enable/disable changes.
automations.set_enabled	Enable or disable one automation without changing its trigger or actions. Enabling requires at least one action and is subject to plan limits. Requires workspace-admin authority and a write-capable credential.
automations.delete	Delete one workspace automation. This archives the rule and stops future executions; it does not undo actions from prior executions. Requires workspace-admin authority and a write-capable credential.
workspaces.list_boards	List a cursor-paginated directory of boards inside a standard workspace. Use boards.list_accessible when the workspace is unknown or the board may be standalone.
workspaces.list_members	List a cursor-paginated directory of a standard workspace's members with userId, displayName, email, and role. Use boards.get to resolve assignees for a standalone board. Requires workspace access.
boards.get_standalone_settings	Read a standalone board's identity, retention, lists, custom fields, labels, templates, and automations using its visible board id. Requires access to the board's configuration; board-only cross-organisation guests cannot use this tool.
boards.get	Get a workspace board or standalone board with its workflow lists, members, labels, and custom fields, but without cards. Use the returned list ids with cards.list to retrieve cards only from the lists needed.
cards.list	Get one bounded page of active (unarchived) cards, including completed cards, from exactly one workflow list. Use boards.get first to resolve the list id, then pass nextCursor to continue. Never returns cards from another list or an unbounded card collection.
search.content	Use this when you need to find live Kanera content by words, phrases, card keys, or filenames. Searches accessible cards, notes, comments, and attachment filenames and returns one relevance-ranked, bounded result stream with source metadata and canonical links.
search.docs	Search official Kanera documentation for product behavior, setup, permissions, and workflow guidance. Returns relevant sections with concise excerpts and canonical source URLs; this does not search the user's live Kanera data.
cards.get	Read a card detail, including labels, assignees, checklist item descriptions, nested sub-checklists, attachments, and linked notes. Checklists are returned flat; a sub-checklist's parentItemId identifies its owning top-level item.
cards.get_content	Read checklist and comment content for up to 200 selected cards in one board, avoiding one detail/comment request per card during summaries, audits, and migrations. Best-effort: ids not visible on the board are returned in missingCardIds, and cards whose bounded comment history is incomplete are listed in truncatedCardIds so comments.list can page them. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board.
cards.list_history	List a card's retained, user-visible history, including comments and activity, newest first. Cursor-paginated and accepts a human key such as PROJ-123. Hidden/coalesced no-op activity and activity outside the configured retention window are not returned.
cards.create	Create a card in one of the board's workflow lists. Works with workspace and standalone boards. Requires board editor access and a write-capable credential.
cards.update	Update one or more card content fields. The required changes object cannot be empty. Requires board editor access and a write-capable credential.
cards.move	Move or reorder a card using one explicit before/after anchor; a null anchor id means that edge. Requires board editor access and a write-capable credential.
cards.duplicate	Copy a card, optionally into another editable board and list. Requires board editor access at the source and destination. This is not idempotent; do not retry after an ambiguous success.
cards.move_to_board	Move a card to another board in the same standard workspace. Standalone boards have no valid destination. Requires editor access to both boards and a write-capable credential.
cards.archive	Archive or unarchive a card. Requires board editor access and a write-capable credential.
cards.set_completion	Mark a card complete or incomplete; completion is distinct from archiving. Requires board editor access and a write-capable credential.
cards.bulk_set_completion	Mark up to 200 selected cards complete or incomplete in one board. Returns changed cards and skipped archived card ids. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
cards.bulk_set_due_date	Set or clear one due date on up to 200 selected cards in a board. Returns changed cards and skipped archived card ids. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
cards.bulk_patch_labels	Add or remove labels on up to 200 selected cards in a board. Returns the number changed, changed card ids, and skipped archived card ids. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
cards.bulk_patch_assignees	Add or remove assignees on up to 200 selected cards in a board. Returns the number changed, changed card ids, and skipped archived card ids. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
cards.bulk_move	Move up to 200 selected active cards to one workflow list in their board. Returns moved cards and skipped archived card ids. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
cards.bulk_archive	Archive up to 200 selected cards in one board. This is destructive and cannot bulk-unarchive. Returns archived cards. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
cards.bulk_duplicate	Duplicate up to 200 selected active cards, optionally to another editable board and list. This is not idempotent: do not retry after an ambiguous success. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access at the source and destination.
cards.bulk_set_custom_field	Set, fill, add, remove, or clear one custom field on up to 200 selected cards. Returns changed values/card ids and skipped archived card ids. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
lists.set_card_completion	Mark every active card in one board/list complete or incomplete. Returns the number changed. Board-scoped: for workspace-wide work, list the workspace's boards and call this separately for each board. Requires board editor access and a write-capable credential.
lists.move_cards	Move every active card from one workflow list to another on exactly one board. Requires board editor access.
lists.archive_cards	Archive every active card in one workflow list on exactly one board. This is destructive and requires board editor access.
cards.set_assignees	Replace all assignees on a card. Requires board editor access and a write-capable credential.
cards.set_labels	Replace all labels on a card. Requires board editor access and a write-capable credential.
cards.set_custom_field_value	Set or clear one custom-field value on a card. Requires board editor access and a write-capable credential.
comments.add	Add a comment to a card, optionally linking card attachments already uploaded for that comment. Requires board editor access and a write-capable credential. This is not idempotent; do not retry after an ambiguous success.
comments.list	List a card's comments, newest first. Cursor-paginated; pass the opaque nextCursor unchanged.
comments.delete	Delete one comment authored by the acting user. Comments from other users, integration credentials, or the system are rejected. This is destructive; use only after an explicit request and, for migrations, after verifying the destination. Requires board editor access and a write-capable credential.
comments.update	Replace the text of a comment authored by the acting user, optionally linking newly uploaded card attachments. Requires board editor access and a write-capable credential.
comments.set_reaction	Idempotently add or remove the connected user's reaction on another person's comment. Requires board editor access and a write-capable credential.
cards.add_attachment	Upload one small file to a card. MCP request limits cap fileBase64 at roughly 512 KiB decoded; use the public API directly for larger files. For a new comment attachment, set source=comment and then include the returned attachment id in comments.add; commentId may link it directly to an existing owned comment.
cards.delete_attachment	Delete a card attachment. If it is the cover, Kanera selects the next eligible image cover. This is destructive and requires board editor access with a write-capable credential.
cards.set_cover	Set one existing image attachment as a card's cover, or pass null to remove the cover. Requires board editor access and a write-capable credential.
checklists.create	Add a top-level checklist to a card, or create a one-level sub-checklist by passing the owning top-level parentItemId. Requires board editor access and a write-capable credential. This is not idempotent.
checklists.update	Rename a checklist. Requires board editor access and a write-capable credential.
checklists.delete	Delete a checklist and its items. This is destructive and requires board editor access with a write-capable credential.
checklists.move	Reorder a checklist using one explicit before/after anchor; a null anchor id means that edge. Requires board editor access and a write-capable credential.
checklists.add_item	Add an item to a checklist. Items in sub-checklists are leaf rows with text and completion only. Requires board editor access and a write-capable credential. This is not idempotent.
checklists.update_item	Update a checklist item's text, completion, description, assignee, or due date. Description, assignee, and due date apply only to top-level items; sub-checklist leaves support text and completion only. Provide at least one field. Requires board editor access and a write-capable credential.
checklists.bulk_update_items	Set or clear the assignee or due date on all items in one checklist. Provide assigneeId or a due date. Repeating the same arguments is idempotent. Requires board editor access and a write-capable credential.
checklists.delete_item	Delete a checklist item. This is destructive and requires board editor access with a write-capable credential.
checklists.move_item	Move or reorder a checklist item, optionally into another checklist, using one explicit anchor. A null anchor id means that edge. Requires board editor access and a write-capable credential.
activity.list	List a cursor-paginated board-wide feed of recent activity and comments.
work.query_history	Use this when reviewing work performed by one person across projects. Returns only that actor's created, moved, completed, and checklist-item-completed events over an exact or calendar range, with full-range counts, source names, canonical card links, and cursor pagination. Omit userId for the connected user.
work.query_cards	Use this when listing current, completed, overdue, unassigned, or stale work across one or many Kanera projects. For another person, use lens=team and one assigneeIds value; do not enumerate boards manually. Results include source-name maps and canonical card links.
work.portfolio_summary	Get bounded organisation, workspace, and board rollups across accessible work, including active, overdue, due-soon, unassigned, completed, and overdue-checklist counts plus recent activity buckets.
priorities.list_targets	List the users whose "Up next" priority queues this credential can read: the connected user plus teammates covered by its effective workspace admin authority. Workspace credentials require admin scope and stay pinned to their workspace. Returns each target's userId, display name, email, authority workspace ids, and live queue size. Write capability still depends on credential scope and per-card authorisation.
priorities.list	List a user's ranked cross-board "Up next" priority queue. Omit targetUserId for the connected user's own queue; a teammate's requires admin authority in a shared workspace (priorities.list_targets shows who is readable). Workspace credentials need admin scope and remain pinned to one workspace. Entries whose card this credential cannot see keep their rank but return card: null. Entry ids are the anchors and handles for the add/move/remove priority tools; mutation separately requires a write-capable credential and per-card authority.
priorities.add	Add a card to a user's "Up next" queue (at most 50 live entries). The card must be assigned to the target user. Your own queue needs only card visibility; a teammate's needs admin authority in the card's workspace. Requires a write-capable credential. Returns the updated queue.
priorities.move	Move one "Up next" queue entry using one explicit before/after anchor; a null anchor id means that edge. Requires a write-capable credential. Returns the updated queue.
priorities.remove	Remove one entry from a user's "Up next" queue without changing the card itself. Requires a write-capable credential. Returns the updated queue.
notes.list	List a cursor-paginated page of flat note metadata. parentNoteId expresses the hierarchy; use notes.get for full content. Provide exactly one of workspaceId for a standard workspace or boardId for a workspace or standalone board. Personal notes are limited to the connected user.
notes.get	Read any visible top-level or nested note. Personal notes are limited to their owner.
notes.get_backlinks	List bounded visible cards, boards, and notes that link to a note.
notes.list_attachments	List a bounded set of files attached to a visible note at any hierarchy level.
notes.create	Create a personal or team note at any supported hierarchy level. The required target explicitly selects a standard workspace or a board. Personal notes are private to the connected user. Team notes require workspace administration or board editor access; creation is not idempotent.
notes.update	Update one or more fields on any visible top-level or nested note. The required changes object cannot be empty. Markdown content can contain external links, Kanera-internal links, and attachment URLs. Team-note edits respect Kanera note locks and require workspace administration or board editor access; personal notes are limited to their owner.
notes.add_link	Append a Markdown link to a note without replacing its existing content. The public API's optimistic timestamp prevents overwriting a concurrent edit.
notes.add_attachment	Upload one small file to a note at any hierarchy level. MCP request limits cap fileBase64 at roughly 512 KiB decoded; use the public API directly for larger files. The returned URL can be added to note content with notes.add_link.
notes.duplicate	Duplicate one visible note, including its Markdown, icon, color, and link relationships. Descendant notes and binary attachments are not copied. The duplicate remains in the same workspace/board and personal/team collection.
notes.move	Reparent or reorder a note within its current workspace/board and personal/team collection. Notes cannot be moved across tenancy boundaries.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

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