# Bevy: MCP server status, API access gate and what it does > Community-event platform for running in-person and virtual community programs at scale (chapter-based... No MCP found, Enterprise only. Checked 2026-08-24. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* --- [Directory](../index.md) / [Community & Dark Social](../categories/community-dark-social.md) / Bevy # Bevy [No MCP found](../mcp/none-found.md) [Enterprise only](../gates/enterprise-only.md) [Community & Dark Social](../categories/community-dark-social.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [https://www.bevy.com](https://www.bevy.com) · entry id 15-bevy · source 15-community-dark-social.md line 254 **What it does** Community-event platform for running in-person and virtual community programs at scale (chapter-based meetups, forums, gamification), used by enterprise brands to formalize community-led-growth events. **AI features, separated from automation with an AI label on it** Markets an "Engagement Agent Hub" (AI-powered community-interaction command center with "Intros AI" matchmaking), a "Community Knowledge Agent," and a "Gamification Agent" for automated reward systems - all vendor-described on the homepage, not independently verified. **RevOps role** Community-event infrastructure layer - less a signal-detection tool than most of this file, but relevant because event/chapter activity is itself a dark-social engagement signal worth tracking. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: none **Access gate** - **Gate bucket**: Enterprise only - **Can a solo operator reach it**: Not without a contract api_gate, verbatim from the file: enterprise-only (inferred) - no public self-serve pricing; the pricing page is a "pricing calculator" reachable only through a "Book a Demo" flow, with add-ons (integrations, SSO, AI features) bundled into a custom quote. **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **Jobs it can do** No job tag on this entry. Reason recorded by the tagging pass: no-job-fits. Community-event infrastructure (chapters, meetups, gamification). Real product, no job in the vocabulary describes running an events programme. Either a new job or an honest permanent blank. 22 of 293 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag. **Sources** - [https://www.bevy.com](https://www.bevy.com) - [http://bevy.com/b/pricing](http://bevy.com/b/pricing) 2 source URLs. Raw sources field, verbatim: https://www.bevy.com, http://bevy.com/b/pricing **Notes, verbatim from the file** Checked github.com, PulseMCP, and bevy.com directly for API/MCP - none found for the community-events Bevy. One PulseMCP hit for "bevy" (aojiaoxiaolinlin/bevy-docs) is an unrelated name collision - it indexes the Bevy Rust game engine's documentation and has no connection to bevy.com. **Provenance** - **Entry id**: 15-bevy - **Source file**: 15-community-dark-social.md - **Source line**: 254 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).