Connection Issues
Plugin Shows 'Disconnected' Status
Plugin Shows 'Disconnected' Status
This is normal behavior when the MCP server isn’t running.
Solution
-
Verify MCP server is installed:
You should see
robloxstudio-mcpin the list -
Restart your AI assistant (Claude Code, Claude Desktop, etc.)
- The MCP server starts automatically when the AI assistant launches
- Click the “MCP Server” button in the Plugins toolbar to activate
-
Check the status steps in the plugin dock widget:
- Step 1 should show “HTTP server reachable (OK)”
- Step 2 should show “MCP bridge connected (OK)”
- Step 3 should show “Ready for commands (OK)”
The plugin will show “Disconnected” until both Studio and the AI assistant are running.
HTTP 403 Forbidden Errors
HTTP 403 Forbidden Errors
This error occurs when HTTP requests are not enabled in your game settings.
Solution
-
Open Game Settings:
- Home → Settings → Game Settings
- Navigate to Security tab
- Enable “Allow HTTP Requests”
-
Restart the plugin:
- Click the “MCP Server” button twice (off then on)
HTTP is OK but MCP Won't Connect
HTTP is OK but MCP Won't Connect
If Step 1 shows “OK” but Step 2 stays on “waiting” for more than 8 seconds.
Symptoms
- “HTTP: OK MCP: …” in status
- Yellow warning indicator
- Troubleshooting tip appears in widget
Solution
-
Close all Node.js processes:
- Windows: Open Task Manager → Find all
node.exe→ End Task - macOS: Activity Monitor → Search “node” → Force Quit
- Windows: Open Task Manager → Find all
- Restart your AI assistant (Claude Code, Claude Desktop, etc.)
-
Wait for connection:
- The plugin will automatically reconnect
- Status should change to “Connected” within 10 seconds
Sometimes Node.js processes stay running after closing the AI assistant. Manually ending them resolves stuck connections.
Connection Lost / Retrying
Connection Lost / Retrying
The plugin shows “Retrying” status or loses connection during use.
Possible Causes
- MCP server crashed or stopped
- AI assistant was closed
- Network or firewall blocking localhost
Solution
- Check if AI assistant is still running
-
Check Studio Output window for error messages:
- View → Output (or press F9)
-
Verify firewall settings:
- Ensure localhost (127.0.0.1) connections are allowed
- Check if antivirus is blocking Roblox Studio
-
Restart both applications:
- Close Roblox Studio completely
- Restart your AI assistant
- Reopen Studio and activate plugin
Firewall Blocking Localhost
Firewall Blocking Localhost
Windows Firewall or antivirus software may block localhost connections.
Solution
-
Check Windows Firewall:
- Control Panel → Windows Defender Firewall → Allow an app
- Ensure Roblox Studio is allowed for Private networks
-
Check antivirus software:
- Some antivirus programs block localhost HTTP connections
- Add exception for
localhost:3002andlocalhost:3001
-
Test localhost connectivity:
Should return a JSON response (may be empty)
Installation Issues
Plugin Not Showing in Toolbar
Plugin Not Showing in Toolbar
The plugin is installed but doesn’t appear in the Plugins toolbar.
Solution
-
Verify file location:
- Windows:
%LOCALAPPDATA%/Roblox/Plugins/ - macOS:
~/Documents/Roblox/Plugins/ - File should be named
MCPPlugin.rbxmxor similar
- Windows:
-
Restart Roblox Studio completely:
- Close all Studio windows
- Reopen Studio
-
Check the Output window (F9) for error messages:
- Errors will appear if the plugin failed to load
-
Try alternative installation method:
- If direct download fails, try the “Save as Local Plugin” method
- See Installation Guide for details
Plugins only load when Studio starts. They won’t appear if added while Studio is running.
Plugin Errors on Load
Plugin Errors on Load
Studio Output shows errors when the plugin loads.
Common Errors
“HTTP 403 Forbidden”- Enable “Allow HTTP Requests” in Game Settings → Security
- Plugin code may be corrupted
- Re-download from GitHub Releases
- Using wrong installation method
- Plugin should be in Plugins folder, not ServerScriptService
Solution
- Check the exact error message in Output window
-
Delete the corrupted plugin:
- Go to Plugins folder
- Delete the plugin file
-
Reinstall using a different method:
- Try Creator Store installation (Method 1)
- Or re-download from GitHub (Method 2)
Server Configuration Issues
Wrong Server Port
Wrong Server Port
The plugin is trying to connect to the wrong port.
Solution
-
Check your MCP server configuration:
- Default port is
3002 - Some setups may use different ports
- Default port is
-
Update Server URL in plugin:
- Open plugin dock widget
- Connection Settings → Server URL
- Change to
http://localhost:YOUR_PORT
-
Verify MCP server is running on that port:
The plugin will automatically reconnect when you change the Server URL.
MCP Server Won't Start
MCP Server Won't Start
The MCP server fails to start with your AI assistant.
Solution
-
Check Node.js installation:
Should show v16 or higher
-
Check npx availability:
-
Manually test MCP server:
Should start without errors
-
Check AI assistant logs:
- Claude Code: Check extension logs
- Claude Desktop: Check console output
-
Try alternative configuration:
Performance Issues
Slow Response Times
Slow Response Times
The plugin takes a long time to respond to AI requests.
Possible Causes
- Large project with many objects
- Complex search queries
- Network latency
Solution
-
Use specific paths instead of scanning entire game:
- Instead of asking for “all scripts”, specify a service
- Example: “List scripts in ServerScriptService”
-
Limit search depth:
- Use maxDepth parameter in queries
- Avoid deep recursive searches
-
Check Activity Log:
- Open plugin dock widget
- Look for slow requests in the log
- Response times shown in milliseconds
-
Monitor Studio performance:
- View → Stats (or press F3)
- Check CPU and memory usage
Plugin Causes Studio to Lag
Plugin Causes Studio to Lag
Studio becomes slow or unresponsive when the plugin is active.
Solution
-
Check Activity Log frequency:
- Excessive polling may indicate a problem
- Should poll every 500ms when disconnected
-
Reduce log verbosity:
- Clear the activity log regularly (X button)
- Poll events are already throttled 10:1
-
Close plugin when not in use:
- Click “MCP Server” button to deactivate
- Stops all background polling
-
Check for infinite loops:
- View Studio Output window for errors
- Uninstall and reinstall plugin if corrupted
The plugin uses long-polling which is very efficient. Lag is usually caused by other factors.
Debug Tools
Activity Log
The built-in activity log helps diagnose issues:- Open the plugin dock widget
- Scroll to “Activity Log” section
- Look for error messages (red text)
- Check connection events (blue text)
- Monitor request timing (cyan and green text)
Export Log
To share logs for debugging:- Click the “E” (Export) button in Activity Log
- Open ServerStorage in Explorer
- Find “MCPActivityLog” StringValue
- Copy the Value property
Studio Output Window
Always check the Output window (F9) for:- Plugin errors on load
- HTTP request failures
- Lua runtime errors
- Connection status messages
Getting Help
If you’re still experiencing issues:GitHub Issues
Report bugs or request features
Configuration Guide
Advanced configuration options
Installation Guide
Try a different installation method
MCP Server Docs
MCP server troubleshooting