Control Discord bot with natural language via MCP server

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

What it is I wanted to create a simple, easy to use, MCP server for your Discord bot(s). How to set up Literally all you do is select your bot auth (or crease a new Discord Bot auth if you havn't e...

Best for

AI Chatbot automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.discordtool, @n8n/n8n-nodes-langchain.mcptrigger, n8n-nodes-base.httprequesttool, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Ashby.

Original n8n.io source

1.1 Workflow description

Title: Control Discord bot with natural language via MCP server
Workflow name: Control Discord bot with natural language via MCP server

What it is- I wanted to create a simple, easy-to-use, MCP server for your Discord bot(s).

How to set up- Literally all you do is select your bot auth (or crease a new Discord Bot auth if you havn't entered your key in n8n before) and that's IT!

How to use it- You can now ask your bot to do things via any MCP client, including from within N8N workflows!

Note: If you need an example, you can check out my simple quickstart Discord MCP Server that uses 4o to send messages to channels on your server and users who are members of the server the bot is in.

Need help? Want access to more workflows and even live Q&A sessions with a top verified n8n creator.. All 100% free?

Join the community

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Send Discord Message to Channel

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 2 - Add Role To Member

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 3 - Remove Role from member

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 4 - Discord MCP Server Trigger

Type / Role: @n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices: Version 1

Block 5 - Get channels of server by server ID

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 6 - Get members of server by server ID

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 7 - Send DM and Wait for reply

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 8 - Send to Channel and Wait for Reply

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 9 - Send DM to User

Type / Role: n8n-nodes-base.discordTool - discordTool
Config choices: Version 2

Block 10 - Get Discord Server IDs

Type / Role: n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices: Version 4.2

Block 11 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 12 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 13 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 14 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 15 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 16 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Control Discord bot with natural language via MCP server
Complexity	advanced
Nodes	16
Categories	AI Chatbot
Author	David Ashby
Published	08 May 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/3946/3946.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source AI Chatbot workflows

Frequently asked questions

What does Control Discord bot with natural language via MCP server do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your AI Chatbot use case.

David Ashby

204 workflows

Nodes

n8n-nodes-base.discordtool @n8n/n8n-nodes-langchain.mcptrigger n8n-nodes-base.httprequesttool n8n-nodes-base.stickynote

Complexity

advanced

Published 08 May 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/3946/3946.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Re-engage missed property viewings with Google Calendar, Gemini, Gmail, and WhatsApp

## Quick overview When a buyer misses a scheduled viewing, this workflow automatically sends an AI-personalized follow-up by email and WhatsApp using Google Gemini, then logs the outcome to Google Sheets, recovering leads that would otherwise go cold. ## How it works 1. Triggers every 15 minutes when a Google Calendar event is updated in the selected viewings calendar. 2. Checks the event title/summary and continues only if it contains the tag “no-show”. 3. Extracts the lead’s name, email, phone, property address, and scheduled viewing time from the calendar event details. 4. Sends the lead and viewing context to Google Gemini to generate an email message and a WhatsApp message in JSON format. 5. Parses and cleans the AI output into safe HTML for email and a trimmed plain-text WhatsApp message. 6. Sends the re-engagement email via Gmail and appends the follow-up outcome to a Google Sheets log. 7. If a phone number is available, sends the WhatsApp message and updates a Google Sheets status field to record that WhatsApp was sent. ## Setup 1. Connect credentials for Google Calendar, Gmail, Google Sheets, and a Google Gemini (PaLM) API key. 2. Select the correct Google Calendar (viewings calendar) and ensure missed appointments are consistently tagged with “no-show” in the event summary. 3. Create or choose a Google Sheets document and sheet, then fill in the document ID/URL, sheet name, and the columns expected by the append/update logging steps. 4. Configure WhatsApp credentials in n8n (or disable the WhatsApp branch) and ensure lead phone numbers are stored in the calendar event description in the expected format (e.g., Name: ... | Email: ... | Phone: ... |). ## Requirements - Before running this workflow, create a Google Sheet with these exact column headers: Record ID | Lead Name | Email | Phone | Property Address | Original Viewing Time | Email Sent | WhatsApp Sent | Email Message Text | WhatsApp Message Text | Timestamp ## Customization - Edit the AI prompt in "Draft Re-Engagement Messages" to change tone or language - Add SMS or other channels by duplicating the WhatsApp branch pattern - Adjust the "no-show" tag keyword if your calendar uses different terminology ## Additional info WhatsApp is optional. If you don't have WhatsApp Business Cloud API credentials, disable that branch — the email follow-up will still send normally. This template assumes calendar events are tagged with "no-show" in the title and include lead contact info in the event description (Name: ... | Email: ... | Phone: ... |).

View

Manage Google Calendar events with Zalo Bot, OpenAI and Gemini

## Quick Overview This workflow lets users manage Google Calendar by sending text or voice messages to a Zalo Official Account bot, transcribing voice notes with Google Gemini and using an OpenAI-powered agent to create, update, list, or delete events, then replying in Zalo with the result. ## How it works 1. Receives an incoming text or voice message through a Zalo Bot trigger. 2. Sends a typing indicator back to the Zalo chat and normalizes key message fields (chat ID, type, text, and voice URL). 3. If the message is a voice note, sends the audio URL to Google Gemini to transcribe it into text. 4. Sends the combined text/transcription to an OpenAI chat model agent that interprets the request in Vietnamese and decides whether to list, create, update, or delete a Google Calendar event. 5. Uses Google Calendar tools to get events and then create, update, or delete the targeted event based on the agent’s extracted parameters. 6. Sends the agent’s Markdown-formatted response back to the user in Zalo, and posts an error message to Zalo if the agent run fails. ## Setup 1. Install the community node package `n8n-nodes-zalo-bot-official` and restart n8n if required. 2. Connect your Zalo Bot API credentials and configure the Zalo webhook URL in your Zalo Official Account so incoming messages reach this workflow. 3. Add a Google Calendar OAuth2 credential and set the target calendar account (currently configured as `[email protected]`) for all calendar operations. 4. Add a Google Gemini (PaLM) API credential for audio transcription and ensure voice messages include a reachable `voice_url`. 5. Add an OpenAI API credential, select the chat model you want to use (currently `gpt-5-mini`), and adjust the system prompt/tone if needed.

View

Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

## Quick Overview This workflow uses Google Sheets, OpenAI, Telegram, and Slack to send post-therapy check-in messages, analyze patient replies for sentiment and risk, alert therapists to at-risk responses, and log non-urgent replies for ongoing wellness tracking. ## How it works 1. Runs every hour on a schedule trigger. 2. Reads session records from Google Sheets and keeps only sessions that have a session date and have not been marked as check-in sent. 3. Uses OpenAI (gpt-4o-mini) to generate a personalized, non-clinical Telegram check-in message from the patient’s session details. 4. Sends the check-in to the patient via Telegram and updates the Google Sheets session row to store the message and mark the check-in as sent. 5. Triggers on incoming Telegram messages, looks up the patient in a Google Sheets master list by Telegram ID, and selects the most relevant recent session to provide context. 6. Sends the patient reply and session context to OpenAI for JSON-formatted sentiment classification and parses the result into structured fields. 7. If the sentiment is classified as at-risk, posts an urgent alert to a Slack channel; otherwise, appends the reply and sentiment details to a Google Sheets wellness log. ## Setup 1. Connect Google Sheets OAuth credentials and update the spreadsheet document ID and sheet names for Sessions, Patients_Master, and Wellness_Log. 2. Create and connect a Telegram bot credential, set up the Telegram trigger webhook, and ensure patient Telegram chat IDs are stored in Google Sheets. 3. Add an OpenAI API key credential and confirm the selected model (gpt-4o-mini) meets your requirements. 4. Connect Slack OAuth credentials and replace the placeholder Slack channel ID used for therapist alerts, and confirm the error-alert channel is set correctly. 5. Verify your Google Sheets columns match the workflow’s expected fields (for example session_id, checkin_sent, checkin_message_sent, therapist_slack_id) before activating.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Control Discord bot with natural language via MCP server

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Send Discord Message to Channel

Block 2 - Add Role To Member

Block 3 - Remove Role from member

Block 4 - Discord MCP Server Trigger

Block 5 - Get channels of server by server ID

Block 6 - Get members of server by server ID

Block 7 - Send DM and Wait for reply

Block 8 - Send to Channel and Wait for Reply

Block 9 - Send DM to User

Block 10 - Get Discord Server IDs

Block 11 - Sticky Note

Block 12 - Sticky Note1

Block 13 - Sticky Note2

Block 14 - Sticky Note3

Block 15 - Sticky Note4

Block 16 - Sticky Note5

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions