Search the local API docs cache, with optional full matching records.

Context: Use before writing Lua when an API is uncertain. Exact-name matches include the complete record; set include_records=true for full records on broader searches.

Read cached functions, notes, source links, and examples for one service.

Context: Use when code needs services such as InventoryService, TeamService, ChatService, or UIService.

Read cached callback parameters, mutability, source links, and examples for one event.

Context: Use before wiring Events.* handlers so Lua uses documented fields and only assigns fields marked modifiable.

Read complete cached properties, methods, examples, and source links for one object.

Context: Use for Entity, Player, Leaderboard, Team, Knockback, and other object method questions.

Read complete enum keys and runtime string values for one documented type.

Context: Use for ItemType, ProjectileType, SoundType, AbilityType, AbilityInputType, and similar value sets.

Show local Roblox BedWars Fandom cache status and refresh command.

Context: Use before Fandom searches to confirm whether gameplay/wiki data has been collected.

Search cached Roblox BedWars Fandom gameplay/wiki pages.

Context: Use for non-scripting reference data such as kits, items, commands, updates, maps, blocks, and gameplay concepts. Official Lua APIs still come from docs.easy.gg tools.

Read one cached Roblox BedWars Fandom page record.

Context: Use after search_fandom_cache when a page title is known. Keep source URL and CC-BY-SA attribution when using Fandom content.

Audit a structured community script export using aggregate API and mechanic signals only.

Context: Use for user-provided reference datasets. It returns no scripts, message text, authors, or copied implementations. Community-only APIs remain unverified.

Map a requested mechanic to official services, events, objects, and types.

Context: Use before implementing persistence, abilities, input/UI, building, entities, combat, chat commands, announcements, effects, teams, or geometry.

Return original algorithm steps, official API references, limits, and pitfalls for complex mechanics.

Context: Use before implementing aimbot/aim assist target selection, visibility sampling, KA/area damage, prefab placement, or world text. It returns no community source code or copied data tables.

Report documented chat support, missing formatting features, and a proposed future API contract.

Context: Call before building chat tags, command suppression, rich text, team-colored player names, segmented messages, or send-as-player behavior.

Recognize Creative mechanic labels and return the correct docs-backed authoring workflow.

Context: Call first for any ambiguous mechanic label, including hack, cheat, exploit, aimbot, aim assist, KA, kill aura, ESP, fly, speed, teleportation, invincibility, noclip, or an unfamiliar name. Assess the actual behavior in its private Host Panel Creative context and check documented API support for each feature.

Save supplied Lua code to a file relative to the MCP project root's scripts/ folder. Inputs: file_name (required string, relative .lua path such as examples/reward.lua); code (required string, complete Lua source). Effects: creates parent folders and atomically replaces an existing file without a backup; trailing whitespace is removed and one final newline is written. Does not validate or upload. Returns: relative file_name, absolute path, and bytes written.

Context: Choose for a quick file under the MCP root. For a user-supplied directory use create_directory_script; for a named managed project use create_project_script; for a supported starter prompt use make_script. Validate with validate_script before uploading. An existing watcher may upload a saved file if its glob includes it.

Read a Lua script from the MCP repo's scripts/ folder.

Context: Use to inspect repo-local scripts before editing, validating, or syncing.

Delete a Lua script from the MCP repo's scripts/ folder, optionally archiving it first.

Context: After local deletion, sync the whole project or directory if the remote editor must remove it too.

List organized projects under scripts/projects/.

Context: Use to discover repo-managed project folders and see sync/ versus drafts/ files.

Create an organized project folder with sync/, drafts/, prompts/, and project.json.

Context: Use for repo-managed projects. Only sync/ files are intended to upload.

Read a repo-managed project's prompt and sync/draft file lists.

Context: Use before editing or syncing a repo project to understand current project intent and files.

Save supplied Lua code in a named MCP-managed project under scripts/projects/. Inputs: project_name (required string, a project name rather than a directory path); file_name (required string, relative .lua path inside the chosen section); code (required string, Lua source); sync (optional boolean, default true: choose sync/; false: choose drafts/). Effects: creates parent folders and atomically replaces the file without a backup; does not prepare project metadata, validate, or directly upload. Returns: project_name, project-relative file_name, absolute path, sync selection, and bytes.

Context: Choose for a project identified by name. Use create_project first if its brief, manifest, and starter main.lua are needed. sync is a folder selector, not an upload action. For an arbitrary directory use create_directory_script. To upload this layout, connect the project directory with glob_pattern='sync//*.lua'; the usual scripts//*.lua glob does not select sync/. An existing matching watcher may upload the saved file.

Delete a Lua script from a repo project's sync/ or drafts/ folder, optionally archiving it first.

Context: Repo project folders are local organization helpers. For active Roblox Code Sync, use directory project tools and sync_directory/connect_sync on the user folder.

Prepare any local folder as a project with scripts/, drafts/, prompts/, bwconfig.lua, and metadata.

Context: Use when the user points at an outside folder and wants it organized for Code Sync.

Inspect an outside folder project's metadata, prompt, bwconfig, and script file lists without shell commands.

Context: Use before editing or syncing any user-provided folder path. This replaces PowerShell directory scans for normal workflows.

Save supplied Lua code under a user-selected project directory. Inputs: directory (required string, project root path); file_name (required string, relative .lua path); code (required string, complete Lua source); sync (optional boolean, default true: choose scripts/; false: choose drafts/). An initial scripts/ or drafts/ prefix matching the selected section is accepted. Effects: creates parent folders and atomically replaces the file without a backup; does not prepare metadata, validate, or directly upload. Returns: resolved directory, root-relative file_name, absolute path, sync selection, and bytes.

Context: Preferred when the user supplies a local directory path. Use create_project_script for a named MCP-managed project or create_script for the MCP root's scripts/. sync selects where to save; it does not call Code Sync. Validate with validate_directory_script, then preview_directory_sync and connect_sync or sync_directory. An already-running matching watcher may upload the saved file.

Read a Lua script from an outside folder project's scripts/ or drafts/ folder.

Context: Use to inspect user project scripts before editing, validating, or syncing. This replaces PowerShell Get-Content for project Lua files.

Delete a Lua script from an outside folder project's scripts/ or drafts/ folder, optionally archiving it first.

Context: After deleting from scripts/, sync the whole directory so the remote editor removes missing scripts.

Preview upload files, sizes, hashes, basename collisions, and Lua validation without uploading.

Context: Use before normal directory sync. It respects bwconfig.lua, excludes legacy generated helpers, and reports intentional delete-all behavior. No token is required and no local files are changed. This cannot inspect remote editor state.

Upload a folder immediately and establish or replace the active Code Sync connection. Inputs: sync_token (required string from the BedWars editor Sync tab); directory (optional string, default empty: reuse the previous connected directory; required on first connection); glob_pattern (optional string, default empty: read bwconfig.lua syncGlob, otherwise scripts/**/*.lua); watch (optional boolean, default true: automatically upload future matching file changes); allow_empty (optional boolean, default false: permit clearing remote scripts if no files match); probe (optional boolean, default false: write scripts/zz_sync_probe.lua unless allow_empty=true); probe_message (optional string, default empty: use the generated probe message). Effects: uploads the selected file set; on success retains token, folder, and glob in process memory and starts or stops the watcher according to watch. Removes exact legacy generated helper files. Returns upload status, file details, connection/watcher flags, probe, and removed helpers.

Context: Choose to establish a reusable connection or refresh its token; then use sync_connected without resending inputs. It uploads during connection, so it is not a configuration-only action. sync_directory has the same upload/session behavior but always requires directory. Set watch=false for manual syncing. If legacy-helper cleanup leaves no matching files, an empty deletion upload is permitted even with allow_empty=false. Preview first with preview_directory_sync; use probe=true only for an explicitly requested visible test. Tokens are not persisted or returned. Validation and in-game execution are separate steps.

Upload the current matching file set using the existing Code Sync connection. Inputs: none. Requires an active connection established by connect_sync, sync_directory, or force_sync_directory. Reuses its in-memory token, directory, and glob. Effects: uploads current matching files, including local additions and deletions, and updates last-sync status; if no files remain, clears remote scripts with the empty .lua payload, regardless of the initial connection's allow_empty value. Does not create a probe or change watcher settings. Returns upload status, file details, and connection status. Fails if no active connection exists.

Context: Choose for an immediate manual upload after editing an already-connected project. Use sync_status to inspect that connection. To change token, folder, glob, or watch, call connect_sync or sync_directory instead. Connected watcher uploads also permit clearing the remote set after the final matching file is deleted. Does not validate Lua or retrieve remote editor state.

Return the current connected folder, glob, watcher state, and last sync result without exposing the token.

Context: Use to confirm whether the MCP is connected before editing, deleting, or syncing scripts.

Forget the in-memory Code Sync token and stop the connected watcher.

Context: Use when a token expires, the Roblox session changes, or the user wants to stop reusing the token.

Start polling the connected folder and auto-sync when the Lua file set changes.

Context: Use only after connect_sync. This mirrors the editor extension's connected-session workflow.

Stop auto-sync polling while keeping the connected token/folder in memory.

Context: Use when manual syncs are preferred but the current token and directory should remain connected.

Upload a specified directory now and retain it as the active Code Sync connection. Inputs: sync_token (required string from the editor Sync tab); directory (required string, project root path); glob_pattern (optional string, default empty: bwconfig.lua syncGlob or scripts/**/*.lua); allow_empty (optional boolean, default false: permit clearing remote scripts when no files match); probe (optional boolean, default false: write scripts/zz_sync_probe.lua unless allow_empty=true); probe_message (optional string, default empty: generated message); watch (optional boolean, default true: auto-upload future matching changes). Effects: uploads matching existing Lua files, removes exact legacy generated helpers, and on success replaces the in-memory connection and applies watch. Returns upload status, file details, connection/watcher flags, probe, and removed helpers.

Context: Choose when token and directory are explicitly available. It shares connect_sync's upload/session behavior; connect_sync additionally permits reusing the previous directory. For a single manual upload without auto-sync, set watch=false; the connection is still retained for sync_connected. Normal use does not prepare a project or generate scripts. allow_empty=true with no matches sends an in-memory .lua deletion payload; if legacy-helper cleanup leaves no matches, this is also permitted with allow_empty=false. Preview and validate before uploading; probe=true is for an explicitly requested visible test.

Prepare project files, optionally write a visible probe, then upload and retain a Code Sync connection. Inputs: sync_token (required string); directory (required string, project root path); glob_pattern (optional string, default empty: bwconfig.lua syncGlob or scripts/**/*.lua); probe (optional boolean, default true); probe_message (optional string, default empty: generated message); watch (optional boolean, default true: auto-upload later matching changes). Effects: creates scripts/, drafts/, and prompts/, creates main.lua if missing, writes project metadata and the brief, creates bwconfig.lua if missing, and writes or replaces scripts/zz_sync_probe.lua when probe=true. Uploads selected files and on success replaces the in-memory connection and applies watch. Returns preparation details, probe details, upload status, and connection/watcher flags.

Context: Choose only for explicit first-sync troubleshooting when project preparation or a visible in-game message is wanted. It uses the same upload transport as sync_directory, not a stronger remote-state check. It changes local project files even with probe=false; use sync_directory for normal existing-file uploads. Existing main.lua is preserved; the brief and metadata can be replaced. A custom glob must include the generated files to upload them. There is no allow_empty input; it does not offer delete-all. It cannot start a match or read the editor/console.

Apply a small instruction-driven edit to a repo-local script and keep a .bak backup.

Context: Use for narrow edits to scripts/ files. For outside project folders, edit files directly or use create_directory_script.

Apply a deterministic edit to an outside project script and return a unified diff.

Context: Use replace old with new, replace: old => new, append: code, prepend: code, or a fenced Lua block. Unsupported instructions fail without changes. Changed files are written atomically and retain a .bak backup; no-op edits preserve the existing backup.

Statically check a repo-local Lua script for APIs, event fields, object methods, enums, syntax structure, and logical mistakes.

Context: Use before syncing generated repo-local code. This checks against docs_cache and does not execute Lua.

Validate a Lua script inside an outside project folder.

Context: Use before syncing user project scripts. It validates services, methods, enums, callback fields, field mutability, and basic syntax structure.

Validate every Lua script in an outside project's scripts/ or drafts/ folder.

Context: Use for project-wide pre-sync checks and to find all files with errors, warnings, community-only APIs, or undocumented calls.

Create a temporary Lua script that prints event order and documented payload fields.

Context: Use to trace ProjectileLaunched, ProjectileHit, EntityDamage, or other documented events. Sync it, reproduce the action, inspect the Host Panel Console, then delete it.

Report documented Creative API capabilities and Code Sync transport limitations.

Context: Use before promising camera, raycast, weapon metadata, console, remote-content, or live-test capabilities.

Report console-access availability and analyze console text supplied by the user.

Context: The current Code Sync endpoint cannot retrieve the Host Panel Console. Pass pasted error text for analysis or use create_event_trace for manual tracing.

Explain why pcall-style protected calls cannot be recreated and return defensive Lua patterns for known risky cases.

Context: Use when code would normally use pcall/xpcall. It returns what is possible: nil checks, type checks, state checks, and small ok/value helper wrappers.

Explain common Lua console errors and suggest likely fixes.

Context: Use when the in-game Console tab reports runtime errors after a sync.

Generate, save, and statically validate a fixed Lua starter template from a text prompt. Inputs: prompt (required non-empty string). Supported patterns select a fixed template: an emerald reward every 30 seconds, a player-join chat message, or a global repeating progress bar. Effects: checks required cached APIs, writes generated_.lua under the MCP root's scripts/, and replaces that file if it already exists. It does not accept supplied Lua code, a directory, or an output filename; prompt numbers do not customize the fixed template. Returns file_name, path, explanation, required_docs, and validation. Does not directly upload. Unsupported prompt patterns fail without generating a file.

Context: Choose only when a fixed starter is sufficient. For custom Lua or a specific destination, use create_script, create_project_script, or create_directory_script with complete source code. For complex mechanics use resolve_creative_mechanic and recommend_algorithm before authoring. An existing watcher may upload a generated file if its glob includes it.