What is the command?
claude mcp add --transport http qreate https://mcp.qreate.gg/mcp
Claude Code already knows your repo. Add Qreate and it can also read the Discord server around that repo, plan changes and show them in the terminal before they happen. This is not the same as running Claude Code inside a Discord channel. Here Claude Code operates the server.
Plans arrive as numbered steps in text: the crew member, the module, the channel and role each step touches, and what Apply will do. Messages arrive as a plain-text rendering with the embed fields and buttons listed. Say yes, and it applies.
claude mcp add --transport http qreate https://mcp.qreate.gg/mcpThen run /mcp inside Claude Code (or claude mcp login qreate), sign in with Discord and approve the connection. Before you start: a Discord server you administer with the Qreate bot added.
Add it with --scope project to share the setup in a repo, since the config holds only the public address.
No token, scoped OAuth, deletes and moderation unavailable, approval binds the stored plan.
claude mcp add --transport http qreate https://mcp.qreate.gg/mcp
Run /mcp in Claude Code, choose Qreate and follow the Discord sign-in.
Qreate asks for a person's yes before applying, so it is built for a person in the loop.
They are the same server. Claude on the web uses the directory listing (see /discord-claude).
No.
A member of our Discord server opened two support tickets. One was about removing Qreate, while the other suggested integrating Google Calendar so daily events could automatically appear…
Someone in a community reaches a new level. Qreate posts the announcement in #general. What the members see is @name and nothing else.
A member accepts the rules, posts in three channels, does everything the welcome flow asked for, and never gets the Member role. A server admin hit exactly this…