Connect an AI tool you already use — such as Claude, ChatGPT, Cursor, or VS Code — to your Bevy community with the Community Assistant. After you sign in and approve permissions, the assistant acts as you, within what your Bevy account can already do.
The Community Assistant uses Model Context Protocol (MCP) so an AI tool can talk to Bevy. You add your community as a connector. The first time, you sign in and choose what the assistant may do. After that, it acts as you — it can only do what your Bevy account can already do, and only with the permissions you approve.
This is different from What is Community Knowledge AI?. Community Knowledge AI lives on the community site and answers questions from your content. The Community Assistant lives in the AI tool and can take action there, such as drafting an event or replying to a post.
Important: The Community Assistant is in beta. Access can be removed, and calls are rate limited. Your community has to have it turned on. Bevy enables it one community at a time. If it is not on yet, contact Bevy Support or your Customer Success Manager.
Before you connect
- Confirm with a community admin that the Community Assistant is turned on for your community. If it is off, the connection fails.
- Use an AI tool that supports remote MCP over streamable HTTP and OAuth sign-in. You do not paste an API key.
- Plan to approve only the permissions you need on the consent screen. Approvals refresh on their own later.
Connect with the install link
Each community that has the feature publishes setup instructions at https://your-domain.com/agent-setup/prompt.md. You can also open Settings → Connected apps on the community site and use the AI assistant setup link there.
The fastest path is to paste this into your AI tool:
install mcp https://your-domain.com/agent-setup/prompt.md
Replace your-domain.com with your community’s domain (include any path prefix your community uses). The setup document is already specific to that community — the assistant follows it and walks you through sign-in.
Tip: Prefer the community endpoint with a trailing slash: https://your-domain.com/mcp/community/. That is the mounted URL. Use the slashless form https://your-domain.com/mcp/community only if the client reports a resource mismatch and asks for that exact string.
Connect by AI tool
If you configure the connector yourself, use https://your-domain.com/mcp/community/ as the server URL:
| AI tool | How to connect |
|---|---|
| Claude Code | Run claude mcp add --transport http your-community https://your-domain.com/mcp/community/, then run /mcp, select the server, and sign in. |
| Claude Desktop or claude.ai | Settings → Connectors → Add custom connector, paste https://your-domain.com/mcp/community/, then connect and approve the consent screen. |
| ChatGPT | Settings → Connectors, and add a custom MCP connector with https://your-domain.com/mcp/community/. |
| Cursor | Add a server entry with URL https://your-domain.com/mcp/community/ in ~/.cursor/mcp.json (global) or .cursor/mcp.json (this project), then authenticate when Cursor prompts you. |
| VS Code | Add a server with type http and URL https://your-domain.com/mcp/community/ in .mcp.json or .vscode/mcp.json, then authenticate. |
| Antigravity | Run agy mcp add your-community https://your-domain.com/mcp/community/, or add the URL in the MCP config, then authenticate when prompted. |
| Other MCP client | Configure a remote streamable HTTP server at https://your-domain.com/mcp/community/ and complete the OAuth consent screen. If the client cannot do OAuth itself, bridge through a remote MCP helper your tool supports. |
After you approve the consent screen, ask something specific, such as which events are coming up in a city, or to summarize the moderation queue.
What the assistant can do
Because the assistant acts as you, it does not get special access of its own. It cannot see attendee lists you cannot see, post as someone else, or moderate a forum you do not moderate.
| Area | Examples (only if your account can already do it) |
|---|---|
| Chapters and events | Look up chapters, events, members, and attendees. Draft or update an event. Check someone in. |
| Discussions | Read, post, comment, edit or delete your own content, react, upvote, tag, and follow. |
| Moderation | Open the flag queue, lock or unlock a thread, pin, merge, and move posts — only in forums you already moderate. |
| Newsletters | List and draft chapter newsletters you are allowed to manage. Sending a live or queued send still follows Bevy’s normal newsletter rules. |
| Search | Search the community, including deeper research across events, chapters, and discussions, plus the leaderboard. |
A few things are not available through the assistant in this release: uploading an event cover image, changing roles and permissions, and controlling a virtual conference.
How access is controlled
- The community must have the Community Assistant turned on.
- You approve what it can access on the consent screen. Reading chapters, writing events, following discussions, moderating, and similar actions are separate approvals.
- Your existing Bevy permissions still apply. Connecting an assistant never grants a higher role.
Anyone can disconnect an assistant from Settings → Connected apps. A community admin can revoke one member’s Community Assistant access without disconnecting everyone else. If access was revoked, every tool call fails even when OAuth still looks successful — ask an admin to restore access. Reinstalling the connector does not fix a revoke.
Fix common connection problems
-
Resource does not match / resource mismatch. Remove a trailing slash from the configured URL only if the client requires the slashless form, or re-add the server with
https://your-domain.com/mcp/community. Keep the trailing slash for browser-based clients. - Connection fails before sign-in. Confirm the Community Assistant is turned on for the community, and that you used your community domain (and path prefix, if any).
- Connected, but every request is rejected. Access was likely revoked, or the account is inactive. Ask a community admin. Reinstalling does not restore revoked access.
- A tool needs a permission you did not grant. Disconnect and connect again so the consent screen can include the newer scopes.