Skip to main content
Glama

dex-mcp

Debug and inspection tooling for Roblox projects, exposed as an MCP server so an AI agent can explore the instance tree, read/write properties, call remotes, and run Luau in a Roblox client driven by an executor.

Repository: https://github.com/972jesko/dex-mcp

Intended use: debugging, inspecting, and learning from your own Roblox projects locally. See GUIDELINES.md.

Install

npm install
npm run build

Run

node dist/index.js

On startup the server prints (to stderr) the local WebSocket URL and a shared token. The Luau bridge connects to that URL. Configure your MCP client to launch node /absolute/path/to/dist/index.js over stdio.

Configuration (environment variables)

Variable

Default

Purpose

DEX_MCP_PORT

8392

WebSocket hub port

DEX_MCP_TOKEN

auto-generated

Shared token required by the bridge

DEX_MCP_ENABLE_WRITE

true

Enable set_property

DEX_MCP_ENABLE_REMOTES

true

Enable remote calling/spying

DEX_MCP_ENABLE_RUN_LUAU

true

Enable run_luau

DEX_MCP_RPC_TIMEOUT_MS

15000

Per-request timeout

The bridge

The Luau bridge that runs inside the executor is documented in its own plan/spec. It connects to the printed WebSocket URL and answers the RPC protocol in docs/superpowers/specs/2026-06-07-dex-mcp-design.md §4.

Available Tools

14 tools
dex_statusA

Report whether the Roblox bridge is connected and basic game info (name, placeId, client version, capabilities).

Inputs: no named parameters.

fire_remoteC

Fire a RemoteEvent (FireServer) with the given arguments.

Inputs: ref (required), args (required).

get_by_pathA

Resolve a dotted instance path (e.g. game.Workspace.Part) to a node with a ref.

Inputs: path (required).

get_childrenA

List the direct children of an instance by ref. Optionally filter by className.

Inputs: ref (required), classFilter.

get_propertiesA

Read the properties of an instance by ref. Property names come from the cached Roblox API dump when available.

Inputs: ref (required).

get_rootA

Get the root instance (game, ref 0) and its top-level services.

Inputs: no named parameters.

get_sourceC

Read the Source of a Script/LocalScript/ModuleScript by ref, if readable.

Inputs: ref (required).

invoke_remoteB

Invoke a RemoteFunction (InvokeServer) with the given arguments and return its result.

Inputs: ref (required), args (required).

remote_spy_dumpB

Return the remote traffic captured since the spy started.

Inputs: no named parameters.

remote_spy_startB

Start logging outgoing remote traffic. Returns an error if the executor lacks the required hooks.

Inputs: filter.

remote_spy_stopA

Stop logging remote traffic.

Inputs: no named parameters.

run_luauB

Execute arbitrary Luau in the Roblox client and return captured output plus a best-effort serialized return value. Power tool.

Inputs: code (required).

set_propertyA

Set a property on an instance by ref. The value is coerced to the property's declared Roblox type when known.

Inputs: ref (required), name (required), value (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct operation: status overview, reading/writing properties, searching, executing code, and remote interaction. No overlapping purposes; fire_remote and invoke_remote clearly differentiate RemoteEvent vs RemoteFunction.

    Naming Consistency5/5

    All tool names use consistent snake_case with a verb_noun structure (get_*, set_*, fire_remote, invoke_remote, run_luau, search). The remote_spy_* prefix uniformly groups spy operations. Only 'dex_status' uses a noun_verb format but it's a single exception.

    Tool Count5/5

    14 tools is well-scoped for a Roblox debugging server, covering inspection, execution, remote manipulation, and monitoring without excessive overlap or missing critical capabilities.

    Completeness5/5

    The tool surface covers the full lifecycle of typical interactions: reading state (get_*, search), modifying state (set_property, run_luau), remote communication (fire, invoke, spy), and monitoring (status, spy). No obvious gaps for its intended domain.

    Related MCP Connectors