cordslite-mcp
OfficialRelated Servers
Alternatives to cordslite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables authorized MCP clients to perform five read-only operations — checking connection status, listing conversations, reading messages, searching, and polling for changes — over selected Discord server channels and DMs, with scope-based authentication, retention limits, and no ability to send messages or moderate.MIT
- FlicenseAqualityCmaintenanceLocal, read-only MCP server that connects to Discord via REST API, allowing listing guilds, channels, and messages with strict access controls and no write operations.5-
- AlicenseNot gradedqualityDmaintenanceA read-only Discord MCP server that allows AI agents to list channels, read messages, and get attachment images from a Discord server for summarization and reporting.181 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to read Discord channels, recent messages, and searchable history, then turn that evidence into freshness-aware team context, briefs, decision baselines, and signed checkpoint diffs through remote MCP and GPT Actions. It keeps Discord access read-only while supporting OAuth/Bearer authentication for multiple clients.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables reading and acting on Discord through your own running desktop client, including messages, direct messages, group chats, threads, forum posts, search, and write operations like sending, editing, reacting, and managing threads.181 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only, provenance-aware research over Discord by pairing an explicitly authorized Discord Desktop local-RPC/OAuth2 path for bounded live channel snapshots with message, thread, and channel search across a locally maintained archive, without writes, deletes, or session-token automation.MIT
TDQS
Scored across 12 tools
Most tools target clearly distinct actions: listing servers, mapping a server, reading messages, searching, fetching attachments, and resolving members. The only mild overlap is between guild_tree and guild_channels, since both describe a server's structure, but their output purposes differ enough to avoid serious confusion.
The naming is readable and mostly thematic, with search tools consistently suffixed as *_search and list tools prefixed as list_*. However, it mixes styles: verb_noun (find_member, fetch_attachment), noun_noun (channel_messages, message_context, guild_tree), and noun_verb (guild_search). The pattern is not chaotic, but it is not consistently applied.
Twelve tools is a reasonable size for a Discord-focused server. Each tool covers a distinct need such as discovery, navigation, message retrieval, search, member lookup, attachment access, and DM support, without feeling padded or redundant.
The toolset provides strong read-side coverage of Discord: guilds, channels, categories, threads, messages, DMs, members, attachments, and search. The main gap is that it is entirely read-only, so sending messages or modifying Discord resources is not possible, but for a search/retrieval-oriented MCP server this is likely acceptable.