
Qreate: Discord community management
io.github.qreate-ggPublished by GitHub account qreate-ggv0.1.0Updated Oct 24, 2026
Build Discord communities with AI: roles, channels, modules, automations and reviewed announcements.
Overview
Lets an assistant build and manage a Discord community: roles, channels, modules, automations and reviewed announcements.
- What you can do
- This remote MCP server connects an assistant to Discord community management through Qreate. According to its description, it covers creating and organizing roles and channels, configuring modules, setting up automations, and handling announcements that go through review. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Worth adding when you run a Discord community and want an assistant to help with its structure and routine management, such as roles, channels, modules and automations. It suits community managers who prefer to draft announcements for review rather than post blindly. It is not aimed at general chat or messaging outside Discord community administration.
- Requirements
- A remote MCP endpoint at over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. No local package or runtime is needed.
Installation
In SourceWeft
- Open Qreate: Discord community management in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.qreate-gg%2Fqreate-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"qreate-discord-community-management": {
"type": "http",
"url": "https://mcp.qreate.gg/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestOct 13, 2026
Score
67% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.