The Discord connector.
Servers, channels, messages and members. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Discord exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Discord defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Discord tool
5 tools, named as the agent sees them.
- list_guildsread
List the Discord servers (guilds) this bot has been added to. Start here: every other tool needs a guild id or a channel id that comes from this one.
- list_channelsread
List every channel in one server. Use it to find the channel id for read_channel_messages. `parent_id` points at the GUILD_CATEGORY the channel sits under. Takes a guild id from list_guilds.
- get_channelread
Get one channel, including its topic and the category it belongs to. Takes a channel id from list_channels.
- read_channel_messagesread
Read recent messages in a channel, newest first. Use it to catch up on a discussion. Takes a channel id from list_channels; page backwards by passing the oldest id you got back as `before`. The bot must be able to view the channel.
- list_guild_membersread
List the members of a server with their nicknames and role ids. Requires the GUILD_MEMBERS privileged intent on the bot — without it Discord returns a 403 and the connector reports that verbatim. Takes a guild id from list_guilds.
Use it from any agent
The same Discord tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Discord Bot Token in your Discord account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Discord once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.