TDA Discord Reader

io.github.targeteddesignagency-blipPublished by GitHub account targeteddesignagency-blipv1.0.0Updated Oct 24, 2026

Discord channel operations for AI agents. Fetch, search, mentions, post. 4 tools.

Overview

AI-generated overview

A local MCP server that gives an AI assistant Discord channel operations: fetching messages, searching, checking mentions and posting.

What you can do
Fetch messages from Discord channels for the assistant to read and summarize. Search channel content for specific terms or topics. Check mentions so the assistant can see where it or a user was referenced. Post messages to Discord channels. Four tools in total, covering these channel operations.
When to use it
Useful when an assistant needs to read, search or post in Discord channels as part of a workflow, for example monitoring a community channel, finding earlier discussion, or sending an update. Only relevant if you work in Discord and want the assistant to act there directly.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not web-executable. No package, authentication, environment variables or headers are declared in the manifest, so how it connects to Discord is not documented here.
Before you install
Posting writes messages into Discord channels, so anything the assistant sends becomes visible to channel members. Reading and searching expose channel content to the assistant and its model provider. The manifest declares no credentials, but a Discord connection would normally need some form of access token; check what it asks for before installing.

Installation

In SourceWeft

  1. Open TDA Discord Reader in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.