Check in: Unit 3 - Verification
This unit proves the full path from your MCP client to Discord. You will authenticate the bot, make a read-only request, discover a channel ID, and send one deliberate test message.
Before involving a model, discord-mcp smoke can verify the same local MCP boot,
authentication, middleware, and Discord REST path deterministically. It is read-only by
default. In an empty private test server, discord-mcp smoke --confirm-write runs a bounded
create/send/edit/delete lifecycle and removes its temporary channel and message.
Where are you going?
Section titled “Where are you going?”The quickstart follows the default progressive surface. It loads each exact contract through
mcp_tools_search, invokes users_get_current and channels_list through
mcp_tools_read, then invokes messages_send through mcp_tools_write in your private
test channel. The first two Discord calls verify the client, token, and real channel ID
without changing Discord.
The final lesson explains the request, validation, execution, and structured result so you can recognize the same flow in every tool reference.
Checklist
Section titled “Checklist”- My bot is installed in the private test server.
- My MCP client has been restarted with the discord-mcp server configured.
- I have the test server ID and a channel where the bot may read and send messages.