# Discord MCP connector

Connect Discord to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can read your servers, channels, members, roles and messages, and post messages and start threads, as the person who signed in.

Source: https://elaichi.ai/connectors/discord/

## Facts

| | |
| --- | --- |
| Application | Discord |
| Category | IM |
| AI tools | 11 |
| Authentication | OAuth or API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Discord is connected

- Summarize what was discussed in the support channel this week
- Who has the moderator role on our community server?
- Post the launch announcement in the announcements channel

## Connect Discord in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Discord.
2. Optionally set Share with, then press Connect.
3. Approve it in Discord. Discord's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Discord tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Discord MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Discord MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Discord MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Discord MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Discord MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Discord to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Discord tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Discord through Elaichi

### Catch up on a channel after the weekend

Community. Ask what was said in the general channel since Friday and get the gist, with the questions nobody answered pulled out so you can reply first.

### Find the member who raised an issue

Support. Look up a member by name, see their roles and recent messages across channels, then post a reply in the right channel without leaving the conversation you are in.

### Post the launch announcement where it belongs

Marketing. Draft the message in plain language, confirm which channel it should land in, and have it posted to your Discord server the moment you say go.

### Turn a bug report into its own thread

Developer relations. When a member describes a problem in a busy channel, start a thread for it so the follow-up stays in one place and the main channel stays readable.

### Check who holds which roles

Moderation. List the members on a server with the moderator or admin role, spot anyone who should no longer have it, and know who to speak to before a change is made.

### Summarize what a thread decided

Events. Ask for the outcome of the planning thread, who committed to what, and the open questions, then post the summary back so everyone works from the same list.

## Elaichi vs Zapier MCP vs Composio for Discord

All three can connect Discord to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Discord tools | Allow or restrict single Discord tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Discord call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Discord to Claude?

Connect Discord in Elaichi first: you either sign in to Discord when prompted or paste an API key, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in as yourself and Discord is ready to use.

### Does Discord work with ChatGPT and Cursor as well as Claude?

Yes. Once Discord is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Discord once and every client you use can reach it.

### What can an AI agent actually do with my Discord data?

With Discord connected, an agent can list your servers, the channels in each one, the members and the roles they hold, and read the messages in a channel. It can also post a message to a channel and start a thread. Short, concrete asks work best, such as the name of the channel and what you want posted, rather than a long paragraph.

### Does connecting Discord give the AI everything on my server?

No. Every call runs as the person who signed in to Discord, so an agent sees only the servers and channels that person can already see, and posts only where that person can already post. Elaichi can narrow that further with restrictions, and it never widens it beyond what Discord itself allows.

### Can my team share one Discord connection?

Yes. One person connects Discord in Elaichi and shares the connection with a team, and nobody else handles a token or an API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who posted which message in Discord, not just which connection was used.

### Can I stop an agent from deleting or changing things in Discord?

This Discord connector cannot delete or edit anything; the only actions that change your server are posting a message and starting a thread. Either of those can be restricted in Elaichi, on a role or on one person, so a team can read Discord but never post. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Discord connection when someone leaves?

Offboarding a person in Elaichi ends their access to Discord through every client at once. If they had shared a Discord connection, it keeps working for everyone else on the team. If you want Discord gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Discord MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Discord is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Discord?

Yes. Both let Claude, ChatGPT or Cursor use Discord. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Discord call.

### How is Elaichi different from Composio for Discord?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Discord: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 11 Discord tools

Every tool below is callable through https://api.elaichi.ai/mcp once Discord is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Discord me** (List). Get information about the current user in Discord. Returns the user object with fields such as id, username, and optionally email if the email scope is granted.
- **List all Discord guilds** (List). Get a list of partial guild objects the current user is a member of in Discord. Returns fields including id, name, icon, banner, owner status, permissions, features, approximate_member_count, and approximate_presence_count.
- **Get single Discord guild by ID** (Get). Get information about a specific guild in Discord. Requires id. Returns guild object including approximate_member_count and approximate_presence_count if with_counts is true.
- **List all Discord guild members** (List). List guild members for the guild with id in Discord. Returns an array of guild member objects representing members of the specified guild.
- **Get single Discord guild member by ID** (Get). Get guild member information for the specified guild_id and id in Discord. Returns a guild member object with user details and membership status.
- **List all Discord guild roles** (List). Get a list of role objects for the guild in Discord. Requires guild id. Returns roles with details including permissions and role attributes.
- **Get single Discord guild role by ID** (Get). Get information about a specific role in Discord. Requires guild_id and id. Returns a role object with details about the role's permissions and attributes.
- **List all Discord channels** (List). List all channels in a Discord server (guild) the bot has been added to.
- **List all Discord messages** (List). List messages in a Discord channel or thread, newest first. The bot needs View Channel and Read Message History in that channel.
- **Create a Discord message** (Create). Send a message as the bot to a Discord channel or thread.
- **Create a Discord thread** (Create). Create a new thread in a Discord text channel. Pass type 11 for a public thread; Discord defaults to a private thread (12).
