Advanced features

Advanced features add capabilities to an existing Stravia setup. They have different prerequisites and access controls; enabling one does not automatically make every model, API key, or client eligible to use it.

Choose a capability

• Web Search : choose between a local agent loop and a separately configured external route. A browser is needed only for a browser-backed local source; other sources may not need Chrome or Chromium.
• Media understanding : select a model able to accept supported image input. This support capability is distinct from a client-facing Model ID.
• Media generation : configure an eligible, enabled image-generation route and its compatible destination. Availability still depends on the connected upstream.
• Credential protection : redact supported text credentials for eligible requests. It does not provide general privacy, database encryption, or protection for every attachment.
• Vendor plugins : review and import a provider-specific WebAssembly component. A trusted plugin may receive connection credentials and make authorized network requests.
• MCP : connect an MCP client to the platform tools exposed by a Server and configure a key with the corresponding MCP permission.

Check eligibility before testing

The relevant model, destination, feature, API key, and upstream may each have their own enablement or capability requirement. Check the specific guide before interpreting an absent model/tool as a connection failure. Do not use a key that lacks the relevant access setting to test MCP or optional injected capabilities.

Understand what a result means

A saved configuration proves that Stravia accepted the settings; it does not prove that an upstream account supports the capability. Usage and quota data may be missing, stale, or provider-specific. Request history and any exported debug data can contain sensitive request content; handle them accordingly.

For everyday model setup, use Core concepts or return to Quick start .