"trello" matching MCP tools:

• preview_importA

  craaftA

  Dry run of import_board: parse a Trello JSON, Jira or Asana CSV, plain CSV or craaft JSON export and return the board it would create (name, columns with card counts, totals, assignee matches, warnings). Writes nothing. For CSV it also returns the headers, the suggested mapping and 3 sample rows; if no title column was guessed, columns come back empty, so pick one and preview again with mapping. This server runs remotely and cannot read your filesystem, so send the file inline. Max 5 MB, 2,000 cards, 200 columns. Attachments are not imported.

  ConnectorOAuth

• bulk_create_tasksA

  WeftA

  Use this when the user wants to import many tasks at once — a CSV/JSON export from Linear, Jira, Notion or Trello, or any list of 3+ tasks from the conversation. Creates the whole batch in ONE call and one database transaction (all-or-nothing) instead of N create_task calls, so it is far cheaper on the monthly AI-call quota. Address columns by semantic ('backlog'/'todo'/'doing'/'done') or name; if the export references cycles/iterations, create the sprints first (create_sprint) and pass their sprintId per task. Tasks land in each column in array order, after the column's existing tasks.

  ConnectorOAuth

• import_boardA

  craaftA

  Create a new board from a Trello JSON, Jira or Asana CSV, plain CSV or craaft JSON export. Call preview_import with the same arguments first and check the result with the user: this always creates a new private board (it never writes into an existing one) and counts toward the workspace's board limit (402 when it is full). Assignees are matched to workspace members by email or username, and matched people get access to the new board; unmatched cards import unassigned. Imported cards send no notifications. Send the file inline. Max 5 MB, 2,000 cards, 200 columns.

  ConnectorOAuth

• api_requestA

  emdlyA

  Call the API of an app the owner connected on emdly (Jira, Trello, Airtable, Pipedrive, Intercom, Stripe, their own API) — emdly adds the owner's access, you never see or need the key. Follow the service's skill (api_list names it) for paths and limits. `path` is relative to the service (Jira: /rest/api/3/search/jql?jql=…, Trello: /1/members/me/boards, Airtable: /v0/<baseId>/<table>?pageSize=50, Pipedrive: /api/v2/deals?limit=50 or /api/v1/…, Intercom: /conversations?per_page=50, Stripe: /v1/invoices?status=open&limit=50). Reading always works (GET, Jira's POST search, Airtable's listRecords, Intercom's POST …/search); changes (other POST/PUT/PATCH/DELETE) only where the owner allowed them on emdly, and only what the owner asked for. For a custom API you sign in yourself as its docs say, writing {{secret}} where the key goes (headers, path or body). Returns the status, paging/limit headers and the body (long bodies are cut — page through).

  ConnectorNo auth

• guideA

  Done BearA

  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.

  ConnectorNo auth

• guideA

  Done Bear MCPA

  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.

  ConnectorNo auth

• create_standalone_projectA

  mFlowA

  Create a new standalone project, seeded with default To Do/In Progress/Done statuses. Use this to start tracking work that has no external tracker — for work already in Jira or Trello, use that provider's own tools instead.

  ConnectorOAuth

• verify_signatureA

  HookdenA

  Verify a webhook signature against a secret — 25 provider-exact schemes plus a generic HMAC mode, the same engine that computes ✓/✗ badges on captures. Covers HMAC-SHA256 (GitHub, Stripe, Svix/Standard Webhooks, Shopify-style base64, URL-signing Square/HubSpot/Trello…), ECDSA (SendGrid), RSA (Kick) and HMAC-MD5 (Patreon). Pass the scheme, the secret, the delivery's headers, and the BYTE-EXACT raw body (body_base64 for binary). The secret is used only for this one in-memory computation — never stored or logged. No bin needed. If verification fails, the #1 cause is a re-serialized body: point the real webhook at a capture bin (create_bin) to get the true raw bytes first.

  ConnectorNo auth

• ask_mflowA

  mFlowA

  Ask mFlow's own AI assistant a natural-language question or request anything not covered by the structured tools — semantic search over your Jira/Trello/standalone data, multi-step actions, or anything ambiguous. This forwards to the same agent mFlow's chat UI uses and can take a while to respond (up to 60s) since it may call several tools internally before answering. May create, modify, or delete data through mFlow's agents. Prefer a structured tool (list_standalone_tasks, create_standalone_task, etc.) whenever one covers the request — it's faster and its effect is predictable from its own schema. Reach for this one when the request needs semantic search, spans several steps, or doesn't map to a single structured tool.

  Connector

  Destructive

  OAuth

• list_knowledge_docsA

  mFlowA

  List knowledge/documentation entries for a project (any project id you use elsewhere with mFlow — Jira, Trello, or standalone), or pass "__global__" for mFlow's own platform-wide docs. Use a returned id with update_knowledge_doc or delete_knowledge_doc.Use this before create_knowledge_doc to check whether a similar doc already exists — there is no update tool yet, so creating again duplicates rather than overwrites.

  ConnectorOAuth

• api_listA

  emdlyA

  List the apps the owner connected on emdly by API key — Jira, Trello, Airtable, Pipedrive, Intercom, Stripe or their own API: name, service, whether you may change data, the skill that explains its API (for a custom API also its base address and the owner's description of it). Pass the name as `app` to api_request.

  ConnectorNo auth

• import_trello_boardA

  DecknoteB

  Creates a board from a Trello JSON export (in Trello: Menu → Print, export and share → Export as JSON): lists, cards with Markdown descriptions, dates, labels, checklists, comments and links. Counts toward the free plan's 5 owned boards.

  Connector

  Destructive

  No auth

• comment_taskA

  classdeskB

  Schreibt einen Kommentar auf eine Karte (wie bei Trello) – z. B. die Antwort auf eine @Claude-Erwähnung. Erscheint in der Glocke der Lehrkraft. Ohne text: liefert Kommentare und Aktivität der Karte (neueste zuerst).

  ConnectorNo auth

• save_task_labelA

  classdeskB

  Legt ein Label im Aufgaben-Board einer Klasse an (wie bei Trello, für alle Karten nutzbar) oder ändert Name/Farbe (mit label_id).

  ConnectorNo auth