Connect Claude to a Bevy community you belong to so you can find events, catch up on discussions, and do your community work without leaving Claude. You sign in with your own community account, and Claude can only do what your account can already do.
The Community Assistant uses Model Context Protocol (MCP), an open standard that lets AI tools like Claude connect to other services. You add your community to Claude as a connector, sign in once, and approve access. After that, Claude acts as you: it sees what you can see and can do what your account can do, nothing more.
If you use a different AI tool, such as ChatGPT, Cursor, or VS Code, see Connect the Community Assistant.
Important: The Community Assistant is in beta, and it only works in communities that have it turned on. If your community doesn't have it yet, ask your community admin.
Before you start
- You have an account on the community and know how to sign in.
- The Community Assistant is turned on for your community. To check, sign in to the community and open Settings → Connected apps. If you see the AI assistant setup instructions link, it's on.
- Your Claude account can add custom connectors. Which Claude plans allow custom connectors is Anthropic's rule — see Anthropic's custom connectors help.
- You know your community's web address, for example
https://community.example.com. Include any path your community uses after the domain.
You don't need an API key or token. You sign in to the community in your browser instead.
Find your community's connector URL
Your connector URL is your community's web address followed by /mcp/community/:
https://your-community-domain.com/mcp/community/
Keep the slash at the end. To see the exact URL for your community, open https://your-community-domain.com/agent-setup/prompt.md (also linked from Settings → Connected apps as AI assistant setup instructions) and copy the URL under Endpoint.
Connect in Claude Desktop or claude.ai
- In Claude, open Settings → Connectors.
- Select Add custom connector.
- Give the connector a name you'll recognize, such as your community's name, and paste your connector URL.
- Select Connect. Your community's sign-in page opens in your browser.
- Sign in with your community account.
- Review the consent screen. It says Claude wants to use your community's Community Assistant with your account, and lists what Claude can see and what it can do for you.
- Select Continue as [your name]. To stop, select Cancel.
Tip: You can't install the connector by typing a command such as "install mcp" in a Claude chat. Claude Desktop and claude.ai need you to add it once in Settings → Connectors.
The consent screen may say This app is not verified. That's because Claude names itself when it connects, so Bevy can't confirm the name. Continue only if you started the connection from Claude yourself.
Connect in Claude Code
- In your terminal, run
claude mcp add --transport http your-community https://your-community-domain.com/mcp/community/. Replaceyour-communitywith any short name you like. To use the connector in every project, add--scope user. - Start a new Claude Code session and run
/mcp. - Select your community's server, then choose Authenticate.
- Sign in to the community in the browser window that opens, and select Continue as [your name].
You can also ask Claude Code to set itself up. Paste this into Claude Code, using your community's address:
install mcp https://your-community-domain.com/agent-setup/prompt.md
Claude Code reads your community's setup instructions and walks you through sign-in. Sign-in opens a browser, so you need to run it in an interactive session.
Check that it works
- In Claude Desktop or claude.ai: your community appears under Settings → Connectors.
- In Claude Code: run
/mcporclaude mcp list. Your community shows as connected, with its tools listed. - On your community: Settings → Connected apps lists Claude as an app you've authorized.
Then ask Claude something specific, such as:
- "What events are coming up in my chapter?"
- "Summarize the latest discussions in the community."
- "Who's on the leaderboard this month?"
What you can do with it
Claude can only do what your community account can already do. It can't see attendee lists you can't see, post as someone else, or moderate a forum you don't moderate.
| What you want to do | Examples |
|---|---|
| Find chapters and events | Look up chapters, upcoming and past events, and event details |
| Take part in discussions | Read threads, post, comment, edit or delete your own posts, react, upvote, tag, and follow |
| Search the community | Search across events, chapters, and discussions, and check the leaderboard |
| Catch up on events you host or moderate | List recordings and download links, and read transcripts and summaries |
| Run a chapter (organizers) | Draft or update events, check people in, and draft chapter newsletters you manage |
| Moderate (moderators) | Work the flag queue, lock, pin, merge, and move posts, but only in forums you already moderate |
Posts and comments Claude makes show your name. Bevy has no undo for changes made through the assistant, so check drafts before you ask Claude to publish or delete anything.
These aren't available through the assistant yet: uploading an event cover image, changing roles or permissions, and running a virtual conference.
About the permissions on the consent screen
Everyone sees the same list of permissions on the consent screen, so it may include some you can't use, such as admin permissions. Approving them doesn't give you any access your account doesn't already have. Your community role and permissions still decide what Claude can do.
If you'd rather Claude not make changes for you, you can still ask it to only look things up, or you can disconnect at any time.
Disconnect Claude
- On your community: go to Settings → Connected apps and disconnect Claude.
- In Claude: remove the connector from Settings → Connectors, or run
claude mcp remove your-communityin Claude Code.
Troubleshooting
| What you see | What to do |
|---|---|
| You typed "install mcp" in a Claude chat and it didn't connect | Add the connector in Settings → Connectors instead. A chat message can't install a connector in Claude Desktop or claude.ai. |
| The connection fails before you get to sign in | Check that the Community Assistant is on for your community (see Before you start) and that you used your community's address, including any path after the domain. |
| Claude reports a "resource mismatch" | Remove the connector and add it again without the slash at the end: https://your-community-domain.com/mcp/community. Only do this if the error asks for it. |
| You connected, but every request is rejected | Your access may have been removed by a community admin, or your account may be inactive. Reconnecting won't fix this. Ask your community admin. |
| Claude says it needs a permission you didn't approve | Disconnect and connect again, so the consent screen can include the newer permission. This also applies if you connected before event recordings were available. |
| Claude can't find a recording or transcript | You can only reach recordings for events you host or moderate. If the transcript or summary still doesn't appear, your community may not have them turned on. |
| Requests start failing after heavy use | The assistant limits how many requests you can make. Wait a few minutes and try again. |
Frequently asked questions
Do I need an API key?
No. You sign in to your community in your browser and approve access. There's nothing to copy or paste except the connector URL.
Can Claude see or do more than I can?
No. Claude acts as you, with your role and permissions in the community.
Is this the same as the AI chat on the community site?
No. The chat on the community site is Community Knowledge AI, which answers questions from community content. The Community Assistant runs inside Claude and can take action for you. See Introduction to Community Knowledge AI.
Who turns the Community Assistant on?
Bevy turns it on one community at a time. If your community doesn't have it, ask your community admin.
Can I connect more than one community?
Yes. Add a separate connector for each community, each with its own name and URL.