MCP Server for Discord automation via Discord Agent Proxy
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-discord-bot","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<!-- Generated by scripts/marketing_readmes.py from README.md; do not edit. --> # MCP Discord Bot Server A Model Context Protocol (MCP) server that provides tools for automating Discord through a self-hosted [Discord Agent Proxy](https://platform.acedata.cloud?utm_source=pypi&utm_medium=referral&utm_campaign=evergreen&utm_content=discord_bot_mcp_package_platform) instance. ## Overview The Discord Agent Proxy is a standalone service you deploy on AceDataCloud. It maintains a persistent connection to Discord using your account credentials and exposes both an MCP and REST API interface. This MCP server wraps the Discord Agent Proxy's REST API, exposing Discord operations as MCP tools for use with Claude, Cursor, and other MCP-compatible AI clients. > ⚠️ **Warning**: Automating a personal Discord account (self-bot) violates Discord's Terms > of Service. Use a dedicated account and keep automation frequency reasonable. ## Prerequisites 1. Create a Discord Agent Proxy application at [platform.acedata.cloud](https://platform.acedata.cloud/console/applications?utm_source=pypi&utm_medium=referral&utm_campaign=evergreen&utm_content=discord_bot_mcp_package_api_key) and activate a subscription. Instance resources are configured automatically; no instance size selection is needed. 2. Enter your Discord account credentials in the configuration page and deploy. 3. In the application's **Overview** tab, confirm the account is connected and copy the MCP endpoint and access token from the Discord account card. A running container does not guarantee a connected Discord account. The **Documentation** tab lists all 14 REST operations with request parameters, response schemas, and code examples. Test `GET /api/whoami` there, or call `discord_whoami` after configuring this MCP server, to verify the connected account. Instance addresses and access tokens are filled in automatically in the console; tokens are hidden by default. Sending, editing, or deleting messages affects the rea…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.