🛠️ Trello tool MCP server 💪 all 41 operations
Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?
Complete MCP server exposing all Trello Tool operations to AI agents. Zero configuration needed - all 41 operations pre-built.
⚡ Quick Setup
- Import this workflow into your n8n instance
- Activate the workflow to start your MCP server
- Copy the webhook URL from the MCP trigger node
- Connect AI agents using the MCP URL
🔧 How it Works
• MCP Trigger: Serves as your server endpoint for AI agent requests
• Tool Nodes: Pre-configured for every Trello Tool operation
• AI Expressions: Automatically populate parameters via $fromAI() placeholders
• Native Integration: Uses official n8n Trello Tool tool with full error handling
📋 Available Operations (41 total)
Every possible Trello Tool operation is included:
🔧 Attachment (4 operations)
• Create an attachment • Delete an attachment • Get an attachment • Get many attachments
🔧 Board (4 operations)
• Create a board • Delete a board • Get a board • Update a board
🔧 Boardmember (4 operations)
• Add a board member • Get many board members • Invite a board member • Remove a board member
🔧 Card (4 operations)
• Create a card • Delete a card • Get a card • Update a card
🔧 Cardcomment (3 operations)
• Create a card comment • Delete a card comment • Update a card comment
🔧 Checklist (9 operations)
• Create a checklist • Create checklist item • Delete a checklist • Delete a checklist item • Get a checklist • Get checklist items • Get completed checklist items • Get many checklists • Update a checklist item
🔧 Label (7 operations)
• Add a label to a card • Create a label • Delete a label • Get a label • Get many labels • Remove a label from a card • Update a label
📝 List (6 operations)
• Archive/unarchive a list • Create a list • Get a list • Get all cards in a list • Get many lists • Update a list
🤖 AI Integration
Parameter Handling: AI agents automatically provide values for: • Resource IDs and identifiers • Search queries and filters • Content and data payloads • Configuration options
Response Format: Native Trello Tool API responses with full data structure
Error Handling: Built-in n8n error management and retry logic
💡 Usage Examples
Connect this MCP server to any AI agent or workflow:
• Claude Desktop: Add MCP server URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • Other n8n Workflows: Call MCP tools from any workflow • API Integration: Direct HTTP calls to MCP endpoints
✨ Benefits
• Complete Coverage: Every Trello Tool operation available
• Zero Setup: No parameter mapping or configuration needed
• AI-Ready: Built-in $fromAI() expressions for all parameters
• Production Ready: Native n8n error handling and logging
• Extensible: Easily modify or add custom logic
> 🆓 Free for community use! Ready to deploy in under 2 minutes.
n8n Trello Tool MCP Server - All 41 Operations
This n8n workflow serves as a Model Context Protocol (MCP) server, designed to expose a Trello tool to an AI model. It acts as a foundational component for AI agents that need to interact with Trello boards, cards, and lists.
What it does
This workflow primarily functions as a trigger for an MCP server, indicating its readiness to receive requests and provide Trello-related functionalities to an AI model.
- Listens for MCP Requests: The workflow starts with an "MCP Server Trigger" node, which is configured to listen for incoming Model Context Protocol requests. This means it's waiting for an AI model to ask it to perform a Trello-related action.
- Exposes Trello Tool: Although the specific Trello operations (the "41 operations" hinted at in the directory name) are not explicitly defined as nodes in this particular JSON, the "MCP Server Trigger" is designed to expose a tool (in this case, a Trello tool) to an AI. The AI would then be able to call various Trello functions through this server.
- Provides a Foundation: This workflow sets up the necessary trigger for an AI agent to leverage Trello capabilities, acting as the entry point for a more complex interaction where the AI can manage Trello entities.
Prerequisites/Requirements
- n8n Instance: An active n8n instance to host and run the workflow.
- Model Context Protocol (MCP) Compatible AI Model: An AI model capable of interacting with an MCP server to utilize the exposed Trello tool.
- Trello Account: A Trello account will be required for the AI to perform actual operations, though credentials for Trello are not part of this specific workflow's JSON. They would be configured in subsequent nodes or the MCP server's environment.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Activate the Workflow: Once imported, activate the workflow. The "MCP Server Trigger" will then be live and listening for requests.
- Integrate with AI Model: Configure your AI model to communicate with this MCP server's endpoint. The AI model will then be able to discover and utilize the Trello tool exposed by this server.
- Extend with Trello Nodes: To implement the actual Trello operations, you would typically add n8n Trello nodes (e.g., "Trello: Create Card", "Trello: Get Board", "Trello: Update List") downstream from the MCP Server Trigger, mapping the AI's requests to specific Trello actions.
Related Templates
Automated YouTube video uploads with 12h interval scheduling in JST
This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. ⚙️ Workflow Logic Manual Trigger — Starts the workflow manually. List Video Files — Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卡/A1-A2). Sort and Generate Items — Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) — Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order × 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) — Iterates over each video item. Read Video File — Loads the corresponding video from disk. Upload to YouTube (Scheduled) — Uploads the video privately with the computed publishAtUtc. Add to Playlist — Adds the newly uploaded video to the target playlist. 🕒 Highlights Timezone-safe: Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. 💡 Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)
By ZaneDetect holiday conflicts & suggest meeting reschedules with Google Calendar and Slack
Who’s it for Remote and distributed teams that schedule across time zones and want to avoid meetings landing on public holidays—PMs, CS/AM teams, and ops leads who own cross-regional calendars. What it does / How it works The workflow checks next week’s Google Calendar events, compares event dates against public holidays for selected country codes, and produces a single Slack digest with any conflicts plus suggested alternative dates. Core steps: Workflow Configuration (Set) → Fetch Public Holidays (via a public holiday API such as Calendarific/Nager.Date) → Get Next Week Calendar Events (Google Calendar) → Detect Holiday Conflicts (compare dates) → Generate Reschedule Suggestions (find nearest business day that isn’t a holiday/weekend) → Format Slack Digest → Post Slack Digest. How to set up Open Workflow Configuration (Set) and edit: countryCodes, calendarId, slackChannel, nextWeekStart, nextWeekEnd. Connect your own Google Calendar and Slack credentials in n8n (no hardcoded keys). (Optional) Adjust the Trigger to run daily or only on Mondays. Requirements n8n (Cloud or self-hosted) Google Calendar read access to the target calendar Slack app with permission to post to the chosen channel A public-holiday API (no secrets needed for Nager.Date; Calendarific requires an API key) How to customize the workflow Time window: Change nextWeekStart/End to scan a different period. Holiday sources: Add or swap APIs; merge multiple regions. Suggestion logic: Tweak the look-ahead window or rules (e.g., skip Fridays). Output: Post per-calendar messages, DM owners, or create tentative reschedule events automatically.
By Takuya OjimaGenerate Funny AI Videos with Sora 2 and Auto-Publish to TikTok
This automation creates a fully integrated pipeline to generate AI-powered videos, store them, and publish them on TikTok — all automatically. It connects OpenAI Sora 2, and Postiz (for TikTok publishing) to streamline content creation. --- Key Benefits ✅ Full Automation – From text prompt to TikTok upload, everything happens automatically with no manual intervention once set up. ✅ Centralized Control – Google Sheets acts as a simple dashboard to manage prompts, durations, and generated results. ✅ AI-Powered Creativity – Uses OpenAI Sora 2 for realistic video generation and GPT-5 for optimized titles. ✅ Social Media Integration – Seamlessly posts videos to TikTok via Postiz, ready for your audience. ✅ Scalable & Customizable – Can easily be extended to other platforms like YouTube, Instagram, or LinkedIn. ✅ Time-Saving – Eliminates repetitive steps like manual video uploads or caption writing. --- How it works This workflow automates the end-to-end process of generating AI videos and publishing them to TikTok. It is triggered either manually or on a recurring schedule. Trigger & Data Fetch: The workflow starts by checking a specified Form for new entries. It looks for rows where a video has been requested (a "PROMPT" is filled) but not yet generated (the "VIDEO" column is empty). AI Video Generation: For each new prompt found, the workflow sends a request to the Fal.ai Sora 2 model to generate a video. It then enters a polling loop, repeatedly checking the status of the generation request every 60 seconds until the video is "COMPLETED". Post-Processing & Upload: Once the video is ready, the workflow performs several actions in parallel: Fetch Video & Store: It retrieves the final video URL, downloads the video file Generate Title: It uses the OpenAI GPT-4o-mini model to analyze the original prompt and generate an optimized, engaging title for the video. Publish to TikTok: The video file is uploaded to Postiz, a social media scheduling tool, which then automatically publishes it to a connected TikTok channel, using the AI-generated title as the post's caption. --- Set up steps To make this workflow functional, you need to complete the following configuration steps: Prepare the Google Sheet: Create a Form with at least "PROMPT", "DURATION", and "VIDEO" fields. Configure Fal.ai for Video Generation: Create an account at Fal.ai and obtain your API key. In both the "Create Video" and "Get status" HTTP Request nodes, set up the "Header Auth" credential. Set the Name to Authorization and the Value to Key YOURAPIKEY. Set up TikTok Publishing via Postiz: Create an account on Postiz and connect your TikTok account to get a Channel ID. Obtain your Postiz API key. In the "Upload Video to Postiz" and "TikTok" (Postiz) nodes, configure the API credentials. In the "TikTok" node, replace the placeholder "XXX" in the integrationId field with your actual TikTok Channel ID from Postiz. (Optional) Configure AI Title Generation: The "Generate title" node uses OpenAI. Ensure you have valid OpenAI API credentials configured in n8n for this node to work. --- Need help customizing? Contact me for consulting and support or add me on Linkedin. Header 2
By Davide