zed -discord

zed-mcp-server-discord is an MCP server extension that bridges Zed with Discord through the mcp-discord integration. It exposes a suite of tools to manage Discord from within the MCP environment, including logging in, sending messages, managing channels, handling forum posts, and working with webhooks. The core tools include: discord_login to authenticate with Discord, discord_send to post messages to channels by ID or name, and discord_get_server_info to retrieve basic server metadata. Channel management tools like discord_create_text_channel and discord_delete_channel let you create or remove channels programmatically. For community interactions, you can use forum-related commands such as discord_create_forum_post, discord_get_forum_post, and discord_reply_to_forum to manage forum content. In terms of messaging, there are utilities to read messages, add or remove reactions, and delete messages. Webhook capabilities allow creating and managing webhooks and sending webhook messages to channels. To use these tools, ensure your MCP environment is connected to this MCP server, authenticate with Discord using discord_login, and then call the desired functions with appropriate parameters (channel IDs, channel names, messages, forum post content, etc.). Carefully handle permissions, as many actions require specific Discord roles or channel permissions.

Prerequisites:

• Node.js (v14+ recommended) and npm installed on your system
• Access to the MCP server environment and network to reach Discord

Installation steps:

1. Clone or download the zed-mcp-server-discord repository to your environment.
2. Navigate to the project directory: cd zed-mcp-server-discord
3. Install dependencies: npm install
4. Configure environment variables for Discord integration. Create a .env file or export variables in your shell: DISCORD_BOT_TOKEN=your-discord-bot-token DISCORD_CLIENT_ID=your-discord-client-id DISCORD_GUILD_ID=your-discord-guild-id
5. Start the MCP server: npm run start or node path/to/server.js (if you use a direct node invocation)
6. Ensure the MCP platform is configured to connect to this server using the provided mcp_config format (see below).

Validation:

• Check logs for successful Discord login and API initialization.
• Use a simple tool call like discord_login and discord_get_server_info to verify connectivity.

Tips and considerations:

• Ensure the Discord bot has the necessary permissions in your server (text channel creation, message management, forum access, webhook permissions, etc.).
• When using channel names, be aware that channel name resolution can be ambiguous if multiple channels share the same name; prefer using channel IDs when possible.
• For forum operations, check that the server supports forum channels and that the bot has access to read and post in those channels.
• Secure your token and client IDs; avoid committing .env files to version control.
• If you encounter rate-limiting from Discord, implement retry logic with exponential backoff in your MCP usage layer.
• This server relies on the underlying mcp-discord integration; ensure compatibility with the version of mcp-discord you’re using.