Announce a release
"Draft a changelog post for v2.4 from this diff, with our banner, for #announcements." Qreate shows the message as Discord renders it. You approve, it posts.
You already keep your bot's config, your docs and your release notes in the repo. Your community's setup can live one pane away. With Qreate as an MCP server in Cursor, the agent can read your Discord server, plan a change and show it to you, while you stay in the editor.
Add Qreate to mcp.json (project .cursor/mcp.json or your global one):
{
"mcpServers": {
"qreate": {
"url": "https://mcp.qreate.gg/mcp"
}
}
}Cursor shows Qreate as needing sign-in. Authorize it, sign in with Discord, and approve the screen that lists your servers. Then ask in Agent chat. Before you start: a Discord server you administer, with the Qreate bot added.
"Draft a changelog post for v2.4 from this diff, with our banner, for #announcements." Qreate shows the message as Discord renders it. You approve, it posts.
"Which of my channels does the ticket panel point at, and are the staff roles still right?"
"Create a dev server for this project: announcements, help, showcase, a contributor role and a rules post."
Ticket panel for bug reports, devlog ping button, changelog posts.
Give the agent an image link, such as a banner in your repo's public assets, and Qreate saves it to the server's asset library for posts and panels. Qreate can also draw a banner after stating the credit estimate.
No bot token in your repo or in mcp.json. The file holds one public address. Sign-in is OAuth and scoped to servers you administer. Delete and moderation actions are unavailable. Applying needs your yes on a stored plan.
Add a url entry under mcpServers in mcp.json, then authorize it when Cursor asks.
Not for Qreate yet. The two lines in mcp.json take a minute.
No. Nothing secret goes in the file.
No. It shows a plan or a draft, and applying needs your yes.
Yes, the config is the same public address. Each person signs in with their own Discord account and reaches only servers they administer.
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…