The Community Assistant lets you connect an AI assistant you already use-like Claude, ChatGPT, or cursor-directly to your Bevy community, so it can look up chapters and events, and with the right permissions, read, post, and help manage your community.
What the Community Assistant is
The Community Assistant is a feature that lets an AI assistant connect to your Bevy community and act on your behalf. It works through a standard called Model Context Protocol, or MCP for short.
Model Context Protocol (MCP) is an open standard that lets AI assistants connect to outside tools and Services, like Bevy, in a consistent way. You don't need to understand the technical details to use it-you'll just add Bevy as a connetor in the AI assistant you already use.
The first time you connect, you sign in to your community and choose what the assistant is allowed to do. From then on, the assistant acts as you: it can only do what you could already do in Bevy, and only with the permissions you approve.
This is different from the Community Knowledge Agent. The Community Knowledge Agent lives on your community site and answers questions using your content. The Community Assistant lives inside the AI tools your team already uses — like Claude or ChatGPT — and can take action on your behalf, such as drafting an event or replying to a post, following the same rules as your Bevy account.
What the Community Assistant can do
Because the assistant acts as you, it can only do what your Bevy account is already allowed to do. It doesn't get special access of its own, so it can't:
- see attendee lists you can't already see
- post as another member
- moderate a forum you don't already moderate
If you can do something in Bevy and you've approved the matching permission when you connected, you can do it from your AI assistant. If you can't, the assistant can't either.
Examples of what you can ask it to do
- Chapter organizers can ask the assistant to list upcoming events in their city, draft a new event in the right chapter, and hold it as a draft until it's reviewed in the dashboard.
- Moderators can ask the assistant to pull the flag queue, see how much content is waiting for review, lock a thread, merge duplicate posts, or pin a reply — only in forums they already moderate.
- Members can search Discussions, follow a tag, upvote an answer, or start a new post from their AI assistant, then open the link Bevy returns to finish in the browser.
How access is controlled
Three things determine what the Community Assistant can do for you:
- Your community must have it turned on. Bevy turns this feature on one community at a time, so it may not be available everywhere yet.
- You must approve what it can access. Reading chapters, writing events, following discussions, and moderating forums are each a separate permission you approve when you connect. These approvals expire and refresh automatically, so you don't need to keep re-entering anything.
- Your existing Bevy permissions still apply. Connecting an AI assistant never gives you more access than your account already has. An organizer can't become a global admin by connecting an assistant.
Tip You can disconnect an AI assistant at any time from Settings → Connected Apps. If you're a community admin, you can also revoke a specific member's access without affecting anyone else's connection. |
Connect an AI assistant to your community
Before you start, check with your community admin that the Community Assistant is turned on for your community. If it isn't turned on yet, the connection will fail.
Every community that has the Community Assistant turned on publishes its own install link, in this format:
https://your-community-host/agent-setup/prompt.md
The exact steps depend on which AI assistant you use:
| AI assistant | How to connect |
|---|---|
| Claude Code | Run: claude mcp add --transport http your-community-community https://your-community-host/mcp/community, then run /mcp and sign in. |
| Claude Desktop or claude.ai | Go to Settings → Connectors → Add custom connector, and paste your community's URL. |
| ChatGPT | Go to Settings → Connectors, and add a custom MCP connector with the same URL. |
| Cursor | Add your community's URL to your Cursor MCP configuration file. |
| Gemini CLI | Run: gemini mcp add --transport http your-community-community https://your-community-host/mcp/community |
After you approve the consent screen, try asking something specific, such as “What events are coming up in London?” or “Show me the moderation queue and summarize why those posts were flagged.”
If the connection fails with a "resource does not match" error, remove any trailing slash from the end of the URL and try again.
If the connection succeeds but every request is rejected, your access has likely been revoked. Reinstalling the connector won't fix this-ask a community admin to restore your access.
What's included today
The Community Assistant currently supports:
- Chapters, events, members, attendees, and event check-in
- Discussions — reading, posting, commenting, editing or deleting your own content, reactions, upvotes, tags, and follows
- Moderation — flag queue, locking or unlocking, pinning, merging, and moving posts
- Search, including deep research over your community's events, chapters, and discussions
- The community leaderboard
A few things aren't available yet:
- Event cover images still need to be set in the dashboard, since the assistant can't upload files.
- Role and permission administration isn't exposed to the assistant.
- Virtual conference controls aren't included in this release.