Skip to main content
TurenOS uses Model Context Protocol integrations to expose external tools and data sources to agents.

​
Deployment types

MCP state is location-scoped. A local Desktop server and a remote server can have different integrations, credentials, and tool inventories. Managed self-hosted services use the Docker MCP runtime by default. Hosted HTTPS integrations connect directly to their reviewed remote endpoint.

​
Demand loading

TurenOS can discover MCP catalogs without loading every tool into each model turn. Selected capabilities are loaded on demand and bounded by the configured tool allowlist.

​
Add a server manually

Use TurenOS configuration for custom MCP servers. Define a unique name, transport, command or URL, headers/environment, timeouts, and enabled state. Keep credentials in declared secret fields rather than checked-in config.

​
Troubleshooting

If a server is disconnected:
  1. Check its Extension status and configuration.
  2. Confirm the local command exists or remote URL is reachable.
  3. Reconnect OAuth when status is Needs Auth.
  4. Review server logs for transport, discovery, or tool-list errors.
See MCP OAuth for hosted authorization flows.