OpenSimulator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENSIM_PATH | No | Path to OpenSimulator installation | ~/opensimulator |
| OPENSIM_CONSOLE_URL | No | URL of the REST console | http://127.0.0.1:9000 |
| OPENSIM_CONSOLE_PASS | No | REST console password | |
| OPENSIM_CONSOLE_USER | No | REST console username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getB | Run a read-only/info/show style command. Examples:
|
| setC | Run a mutating/management command (set/change/restart/save/etc.). Examples:
|
| runA | Run any raw OpenSimulator console command. Use this for commands not covered by get/set categorization. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: 'get' for read-only/info/show commands, 'set' for mutating/management commands, and 'run' as a fallback for any raw console commands not covered by the other two. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the intended action.
All tool names follow a simple, consistent verb pattern: 'get', 'run', and 'set'. They are short, clear, and uniformly styled without any mixing of conventions, making them predictable and easy to understand for an agent.
With only 3 tools, the server feels thin for managing an OpenSimulator console, which typically involves many commands. However, the tools are well-scoped to cover read, write, and raw command categories, making the count borderline but functional for basic operations.
The tools provide a complete surface for the domain by categorizing commands into read-only ('get'), mutating ('set'), and a catch-all ('run') for any other console commands. This covers the core workflows of OpenSimulator management, though some specific operations might require using the raw 'run' tool instead of dedicated tools.