cursor-discord-channels
Provides tools for interacting with Discord channels, including sending replies, fetching messages, and access control, enabling AI agents to manage Discord conversations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cursor-discord-channelsFetch recent messages from #general channel"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cursor-discord-channels
Talk to your cursor agents in Discord, get the work done
Discord bridge + MCP tools for Cursor. When someone @mentions your bot, a small bridge wakes the Cursor CLI agent (Composer by default); the bridge posts the reply as your bot (default), or the agent can use Discord MCP tools in legacy mode.
Discord → bridge → cursor agent → bridge posts reply (default)
↳ or Discord MCP when CDC_BRIDGE_OUTBOUND=mcpUses your Cursor subscription — no separate API bill. No VPS required to get started.
Choose your setup
Local (start here) | VPS (always-on) | |
Cost | No VM — subscription only | ~$5–10/mo server |
Difficulty | Easiest ( | SSH + systemd |
RAM | Shared with your laptop; scales with concurrent agents | Uses server RAM |
Uptime | Mac powered on, no sleep (lid closed OK with | 24/7 without your machine |
Agents | 2–3 bots usually fine; 4+ strains RAM & thermals | Many bots / workspaces |
Guide |
Related MCP server: discord-mcp-agent
Quick start (local)
git clone https://github.com/lilyzhng/cursor-discord-channels.git
cd cursor-discord-channels
npm installCreate a Discord bot → save token to
~/.cursor/channels/discord/.envagent loginexport CURSOR_CWD=/path/to/your/projectandexport CDC_STATE_DIR=~/.cursor/channels/discordnpm run bridge— orbash scripts/start-bridge-local.shfor background
Full walkthrough: docs/LOCAL_SETUP.md
What you get
@mention your bot → real reply in the thread
Subscription auth — same quota as Cursor IDE / CLI
Access control — pairing, allowlists, trusted bots
Self-hosted — your token, your rules
Benchmarks
Measured on a live server against the real agents. The warm ACP session (v0.2) cuts steady-state latency from ~10 to 12s (cold spawn per message) to ~1.2 to 2.5s, roughly 5 to 10x, and adds shared cross-channel memory.
We also raced three models on one full agentic task (read PR #5 → author an SVG →
render with rsvg-convert → post the image back to Discord):
Agent | Model | Time |
Jackie | Composer 2.5 | 42.3s |
Lucy | Sonnet 4.6 | 72.0s |
Andrej | Opus 4.8 | 103.0s |
Composer 2.5 won on speed and held up on quality; Opus produced the richest-looking diagram. Full writeup, the three diagrams, and the shell-harness root-cause fix: docs/BENCHMARKS.md.
More help
docs/DISCORD_BOT.md — create a bot in Discord Developer Portal (start here if new)
docs/LOCAL_SETUP.md — Mac/laptop + nohup (recommended first)
docs/VPS_SETUP.md — systemd, multi-agent on a server
docs/AUTH.md — subscription vs API key
docs/BENCHMARKS.md — warm-bridge speedup + cross-model agentic race
skills/discord-access/SKILL.md — who can talk to the bot
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lilyzhng/agent-channels'
If you have feedback or need assistance with the MCP directory API, please join our Discord server