MCPBridge MCP Server

Unified MCP server bridging Claude Code and Ollama to Roblox Studio and Blender.

Local serverstdioPython

What is the MCPBridge MCP server?

Unified MCP server bridging Claude Code and Ollama to Roblox Studio and Blender. The mcpbridge mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

These steps are required regardless of your platform or install method.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

  • studio_status — Check if the Roblox plugin is connected
  • studio_list_scripts — List all scripts in the place
  • studio_read_script — Read a script's source code
  • studio_write_script — Overwrite a script's source
  • studio_create_script — Create a new script instance
  • studio_execute_lua — Execute Lua in the plugin context
  • studio_get_output — Get recent print/warn output
  • studio_get_workspace_info — Get place metadata
  • studio_get_selection — Get currently selected instances
  • blender_status — Check if the Blender plugin is connected
  • blender_execute_python — Execute Python (bpy) code in Blender
  • blender_get_scene_info — Get scene objects, active object, render settings

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCPBridge.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcpbridge mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCPBridge's toolset — studio_status, studio_list_scripts, studio_read_script and 11 more — is a fair guide to whether it matches your workflow. It is maintained by iamjrmh; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCPBridge's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
studio_statusCheck if the Roblox plugin is connected
studio_list_scriptsList all scripts in the place
studio_read_scriptRead a script's source code
studio_write_scriptOverwrite a script's source
studio_create_scriptCreate a new script instance
studio_execute_luaExecute Lua in the plugin context
studio_get_outputGet recent print/warn output
studio_get_workspace_infoGet place metadata
studio_get_selectionGet currently selected instances
blender_statusCheck if the Blender plugin is connected
blender_execute_pythonExecute Python (bpy) code in Blender
blender_get_scene_infoGet scene objects, active object, render settings
blender_get_outputGet recent output captured by the plugin
ollama_generate_pythonGenerate Blender Python for a task, optionally execute it

How to install the MCPBridge MCP server

{
  "mcpServers": {
    "mcpbridge": {
      "command": "npx",
      "args": ["-y", "@iamjrmh/mcpbridge"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use MCPBridge to studio status.
  • Use MCPBridge to studio list scripts.
  • Use MCPBridge to studio read script.

Frequently asked questions

It connects MCPBridge to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (studio_status, studio_list_scripts, studio_read_script, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCPBridge directly.