OGSync
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OGSyncsync src folder with Studio"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OGSync
AI agent framework for Roblox Studio: a token-lean MCP server, two-way live script sync, and a self-installing Studio plugin — one binary.
MCP server — replaces the official Roblox Studio MCP (and covers the ~100-method community surface) with ~20 consolidated, batch-first tools designed for minimal token usage.
Two-way sync — filesystem ⇄ Studio, live, including Team Create collaborator edits. Rojo-compatible project format.
Zero-friction install — the CLI installs and hot-updates the Studio plugin automatically; the CLI updates itself from GitHub Releases.
Install
Download the binary for your platform from Releases, unzip it, and put it on your PATH. It updates itself from then on.
Related MCP server: rbxsync-mcp
Quick start
cd my-roblox-project
ogsync init # scaffold ogsync.toml + default.project.json + src/ (skip if you already use Rojo)
ogsync serve # daemon: MCP over stdio + Studio bridge + two-way syncserve installs the Studio plugin on first run. Restart Studio so it picks
the plugin up, then open your place — the OGSync button in the Plugins tab shows
the connection panel.
Register it with Claude Code:
claude mcp add ogsync -- ogsync serveor by hand:
{ "mcpServers": { "ogsync": { "command": "ogsync", "args": ["serve"] } } }When something is not connected
ogsync doctorChecks the project file, the installed plugin, the daemon, the Studio binding and sync state, and tells you the next action for anything failing.
Choosing which Studio instance to drive
With several places open, pin one in ogsync.toml — the daemon binds to exactly
that session and never touches the others:
[bind]
target_place = "MyPlace" # place name or place idCommands
| daemon: MCP + bridge + sync ( |
| scaffold config and project files |
| diagnose the setup |
| query the running daemon |
| manage the Studio plugin file |
| check GitHub Releases now |
Docs
docs/DESIGN.md— architecturedocs/TOOLS.md— the MCP tool contractdocs/PROTOCOL.md— daemon ⇄ plugin wire protocoldocs/PLUGIN_CONTRACT.md— plugin module contract
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/joxan2137/ogsync-sync'
If you have feedback or need assistance with the MCP directory API, please join our Discord server