桥 qiáo 🌉
bridge, n. — a structure carrying a road or path over a river, road, or other obstacle; a connection between two places.
桥：名词。跨越河流、道路等障碍以供通行的建筑物；比喻连接两处的纽带。
a bridge between the grid and any tool that speaks model context protocol
the model context protocol (mcp) server lives inside the main server, and because the hub keeps a live websocket to every bot, the mcp endpoint reaches them in-process — no extra bridges, no extra network hops.
mcp client (agent / operator tooling)
| http post /mcp (streamable http)
v
inworld-hub (server/mcp.luau + hub.luau)
| websocket relay (bot.eval / bot.run)
v
bot processes (embedded luau vm + client.* bindings)
ai assistants and scripts inspect grid state, trigger movement, manage marketplace listings, and run standing services through plain mcp tool calls
protocol & framing
- endpoints:
http://127.0.0.1:8300/mcp (prod) | :8301 (staging).
- transport: streamable http (
post /mcp); mcp spec 2025-06-18 over json-rpc 2.0.
- framing: requests with an
id return a json-rpc result/error; notifications (no id) return 202 accepted.
- errors: failures inside a tool return a normal result with
isError = true and details in the text block.
client configuration
{
"mcpServers": {
"inworld-hub": {
"type": "http",
"url": "http://127.0.0.1:8300/mcp"
}
}
}
the tools, in brief
management: bots_list, bot_eval, bot_run, ans_salt, bot_services, bot_service
typed grid ops (wrappers over bot_eval): bot_chat, bot_im, bot_rez, bot_teleport, bot_region_state, bot_read_inventory, bot_sit, bot_stand, bot_pay, bot_friends, plus event push (bot_subscribe, bot_unsubscribe, bot_events, bot_subscriptions).
every bot_eval/bot_run runs inside a resumable luau coroutine on the bot's worker thread. async calls without a callback yield the coroutine; the vm resumes on the correlated reply — the worker stays free during the wait.
the full tool reference — every signature, arg, and behavior — lives at dev.inworld.help/mcp. this is the short version.