Skip to main content
Open Extend from the navigation rail to browse the TurenOS Extensions catalog. Extend is the app destination; Extensions are the capability packages you install and manage there. An Extension manifest can contribute:
  • A local, hosted, or customer-URL MCP server
  • A reviewed local command or security scanner
  • A read-only data source
  • An agent skill
  • Configuration fields and secret declarations

​
Install and enable

Available Extensions can be installed and enabled. Enabled entries show runtime status such as Connected, Needs Auth, Blocked, or Failed. Manage an installed entry to update configuration, credentials, or enabled state. Fieldless hosted OAuth cards showing Needs Auth connect directly when clicked. Entries that need a URL, tenant, or secret open configuration first.

​
Trust model

A manifest describes capability but does not grant arbitrary authority. Runtime adapters, tool allowlists, location permissions, and provider connection policy remain the enforcement boundary. Unknown MCP tools are blocked unless the manifest or trusted configuration declares them. Self-hosted managed MCP services use the Docker MCP runtime unless you explicitly select the trusted local-process backend.

​
Defaults

Official built-in Extensions ship with TurenOS. Some are enabled by default; others require installation, credentials, local binaries, or explicit activation.