messages_fetch
One message read live from Discord — the text, embeds, reactions, freshly signed attachment links and reply header it has right now — for when the stored copy has gone stale
How to use it
Project documentation lists messages_fetch for the Discord Manager MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
FULL DISCORD MANAGER LISTINGOther tools in Discord Manager (19)
Whether the store recorded anything after an instant — counts and newest timestamps for new messages, pings of you or of your bot, and bookmark additions, on the store's own clock, with no content — answering at once, or holding the call open until something lands
A reason of your own, on top of the ones you started with
A reason reworded, on every bookmark already carrying it
The reasons you can file bookmarks under, with how many bookmarks each one holds
A reason taken out of circulation, without disturbing the bookmarks that carry it
A bookmark from a Discord message link, filed under the reason you pick
The bookmarks still waiting on you, each with its reason, its text, the text of any embeds it carries, what is attached to it, the reactions still on it, and, when it is a reply, which message it answers — snoozed ones and single-reason views on request
A bookmark cleared, leaving any reaction in Discord untouched
A bookmark filed under a different reason — how an unsorted 🔖 capture leaves the Inbox
A bookmark hidden until the moment you pick
The channels the bot can see, with the name each one carries now, plus its topic, category and position when it has them — and for threads, whether Discord has archived them, archived ones last
Whether the bot is receiving from Discord, and how far backfills have got
The people the bot has seen post in your server, each with the discordUserId a <@id> mention needs and the username and display name they go by now — matched on part of a name in any case, or taken whole
The messages that pinged you or your bot since a moment in time — someone naming either of you, plus replies the sender left the ping on — each with its text, the text of any embeds it carries, what is attached to it, the reactions still on it, and, when it is a reply, which message it answers
Everything posted since a moment in time, across the server or in one channel, 200 at a time — each message with its text, the text of any embeds it carries, what is attached to it, the reactions still on it, and, when it is a reply, which message it answers
How many messages match and nothing else — a total, the first and last matching timestamps, and a count per UTC day when you ask for one — narrowed by channel, by text in a message or its embeds, and by a window, over as much history as the store holds
A message posted to a channel as your bot, optionally as a reply to a message in that same channel, or as a guarded retry of an earlier send
Where a send ended up — delivered, skipped, failed, still on its way, or stalled when nothing was ever recorded — whether it can be retried, and every attempt already made at it
A public thread created in a channel, or anchored on a message the bot has ingested, with a channelId of its own to post into and the link that opens it in Discord