World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Version-accurate Bevy API docs, Book, migration guides and examples for AI agents.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 15/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 27/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Bevy Manual MCP yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect Bevy Manual MCP yet
The maker has not listed install details in the MCP Registry yet
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Bevy Manual MCP yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect Bevy Manual MCP yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect Bevy Manual MCP yet
The maker has not listed install details in the MCP Registry yet
BEVY_PROJECT_ROOT envBEVY_VERSION envBEVY_MCP_DATA_DIR envBEVY_MCP_OFFLINE envBEVY_MCP_INDEX_BASE_URL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
cargo: bevy-manual-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account kinkirill, which owns the repo
Code last changed 20 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/kinkirill-bevy-manual-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 20 days ago, and the latest version (0.5.2) reached the registry 20 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Rust on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Bevy Manual MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
This MCP was designed by a human and built using AI tools to increase development speed.
Bevy is a fast-moving project that changes with every release. Its documentation is large and scattered, so finding an answer that actually matches *your* version often means digging through rustdoc signatures, the Bevy Book, migration guides, release notes and runnable examples - and still landing on something written for a different release. This server tries its best to remove that friction.
You ask your agent a question and it answers from knowledge pinned to the exact Bevy version your project is using.
Key points:
mcp-name: io.github.kinkirill/bevy-manual-mcpbevy_validate_systems is a syntax-level linter, compatibility can be "unknown", and missing metadata is reported as missing.cargo install bevy-manual-mcp
Requires a Rust toolchain. There is no prebuilt binary matrix and no npm shim.
The server starts answering immediately. If the detected Bevy version has no installed index, it downloads the prebuilt bundle in the background (progress on stderr) and reloads the index when the install completes. To install it explicitly before starting the server:
bevy-manual-mcp fetch-index 0.20.1
bevy-manual-mcp status
Index releases are per Bevy minor (v0.20); an exact-patch corpus is used when present, otherwise the same minor's newest corpus answers for the patch. Status, search results and resources report both the project version and the corpus version that actually supplied the data. BEVY_MCP_OFFLINE=1 disables all downloads, including the background fetch.
The bare command is the MCP server (stdio), exactly as MCP clients launch it.
bevy-manual-mcp # serve MCP over stdio
bevy-manual-mcp serve # explicit form bevy-manual-mcp --help bevy-manual-mcp status # detected version, corpus state, paths bevy-manual-mcp versions # installed corpora bevy-manual-mcp search "system ordering" bevy-manual-mcp lookup Query::iter --json
Most clients only need a command:
{
"mcpServers": { "bevy-manual-mcp": { "type": "stdio", "command": "bevy-manual-mcp", "env": { "BEVY_PROJECT_ROOT": "/path/to/your/bevy/game" } } } }
BEVY_PROJECT_ROOT is optional if the client's working directory is the Cargo project; the version is read from Cargo.lock first and Cargo.toml second.
| tool | what it answers |
|---|---|
bevy_search | Hybrid API + prose search: signatures, Book, guides, examples |
bevy_api | Exact symbol lookup with the real signature, docs and related items |
bevy_examples | Runnable engine/Book examples for a task |
bevy_migration | Breaking changes between two Bevy versions |
bevy_api_diff | One symbol across the compiled versions you name |
bevy_check_version | Newest published Bevy, patch vs breaking, pre-releases |
bevy_indexed_versions | Which Bevy versions this install can answer for |
bevy_index_status | Self-diagnosis: active version, corpus, paths |
bevy_mcp_check_release_index | Whether this server's GitHub index release has a newer corpus/revision |
bevy_check_manifest | Enabled Cargo features and whether a symbol is available |
bevy_validate_systems | Syntax-level B0001/B0002 lint (tuple-aware, filters) |
bevy_explain_error | Explain a pasted panic/warning, version-checked |
bevy_ecosystem_search | Fan-out over the Bevy corpus and installed plugin corpora |
bevy_ecosystem_compat | Plugin ↔ Bevy compatibility from the vendored snapshot |
bevy_generate_plugin | Self-contained plugin scaffold, parsed with syn |
bevy_perf_advisor | Performance topics and is_changed/is_added detection |
bevy_validate_systems does not type-check and cannot decide Bevy runtime panics; it recognises the B0001/B0002 access patterns and says when its analysis is incomplete. bevy_generate_plugin reports compile_verified: false because no compiler runs. bevy_ecosystem_compat is offline-only and returns compatible: "unknown" for requirement operators it does not evaluate.
The server also exposes bevy:// resources and templates:
bevy://index/versions
bevy://api/ / bevy://kind/ / bevy://module/ / bevy://crate/ / bevy://owner/ / bevy://doc/ /
Listings page at 50 items with query-bound cursors; reads open the requested version on demand.
File (bevy-mcp.config.json), environment and defaults combine in that order; environment variables win.
| variable | meaning |
|---|---|
BEVY_PROJECT_ROOT | Cargo project used for version detection |
BEVY_VERSION | Explicit version override, e.g. 0.20.0 |
BEVY_MCP_DATA_DIR | Persistent corpus directory (default ~/.cache/bevy-mcp/data) |
BEVY_MCP_OFFLINE | 1 disables downloads |
BEVY_MCP_INDEX_BASE_URL | Mirror for fetch-index releases |
BEVY_DOC_DIR | Local rustdoc tree for build --doc-dir |
BEVY_WEBSITE_DIR / BEVY_EXAMPLES_DIR | Local prose/examples sources for rebuilds |
BEVY_META_DIR | Vendored bevy-meta root (feature graphs, error codes) |
BEVY_MCP_COMPAT_PATH | Explicit compat.json path |
BEVY_MCP_MAX_RESULTS | Default result count, 1–20 |
BEVY_MCP_DEBUG | 1 for timing/progress diagnostics |
The config file additionally accepts a corpora array for plugin corpora:
{
"corpora": [ { "crate": "bevy_egui", "version": "0.43.1" }, { "crate": "bevy_rapier3d", "auto": true } ] }
Plugin corpora live under data/corpora/ / / and are built with the normal build command.
# From a local `cargo doc` tree (or a docs.rs mirror)
bevy-manual-mcp build --doc-dir target/doc
bevy-manual-mcp build --records records.ndjson --out data/versions/0.20.0
bevy-manual-mcp build --doc-dir ~/.cache/bevy-mcp/bevy-0.20.0 \ --pack dist/bevy-0.20.0-fmt1.tar.zst \ --manifest dist/index-manifest.json
A full 0.20.0 rebuild from 8,665 rustdoc pages takes ~30 s in release mode and produces exactly the canonical corpus: 253,196 records, 653,264 symbol keys, 15.2 MB tantivy index. See GETTING-API-DOCS.md and HOW-IT-WORKS.md.
See docs/DEVELOPING.md for the layout, tests, index rebuilds and release process.
MIT. Vendored Bevy metadata and website prose are covered in docs/THIRD-PARTY-NOTICES.md.