OGSync
Enables AI agents to interact with Roblox Studio via a token-efficient MCP server, live two-way script sync, and zero-friction plugin setup.
README
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.
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 sync
serve 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 serve
or by hand:
{ "mcpServers": { "ogsync": { "command": "ogsync", "args": ["serve"] } } }
When something is not connected
ogsync doctor
Checks 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 id
Commands
ogsync serve |
daemon: MCP + bridge + sync (--no-mcp, --port N) |
ogsync init |
scaffold config and project files |
ogsync doctor |
diagnose the setup |
ogsync status |
query the running daemon |
ogsync plugin install|uninstall |
manage the Studio plugin file |
ogsync update |
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.