MCP integrations
Connect compatible agent clients to your own protected instance.
Start with your instance’s MCP settings
Open Settings → MCP on your own MSO instance. It shows the actual server URL, discovery probes and client-specific steps. This public website does not host an MCP server.
Use the live settings and current source reference for OAuth registration, callbacks and client configuration.
The runtime switch
MCP routes are disabled unless OS_MCP_ENABLED=1 is active in the running process. Demo mode forces MCP off. Fresh installer configuration can enable it; existing configuration is preserved.
A 404 on MCP or discovery can mean the runtime switch is off. Do not treat that response as proof of a DNS failure.
Pick the least authority you need
MCP scopes are read, write and exec. Consent and the runtime ceiling both constrain access. OAuth/PKCE, exact registered callbacks and device approval remain part of setup.
Only connect a trusted client to the intended instance. Host-changing tool calls can use the owner’s authority.
Client setup and OAuth field mapping →These guides orient you; use the runtime reference for complete flags and operational procedures.
Read docs/MCP.md on GitHub ↗Reviewed against source 5c4f136a.