settings.vims

Configuration

Settings: models, keys, MCP, and voice

Configure providers and local models, store API keys locally, connect MCP servers, tune voice and personality, set agent policy, and manage updates.

Open SettingsDownload VIMS

Inside VIMS Desktop · macOS · Windows · Linux · ChromeOS · Free

Sandbox policyokCredential scanokTool approvalsokAudit logok

What it does

Settings is where the platform is wired: which models answer, which keys are used, which MCP servers auto-connect, how voice and personality behave, and what agents are allowed to do.

01
Models and providersOllama, OpenRouter, and direct provider keys.
02
API keysStored in the local keystore, injected into tools and MCP servers.
03
MCP serversAdd, connect, and auto-start servers.
04
Voice and personalityWake word, voices, and persona.
05
Security and policyAgent defaults and approval rules.
06
UpdatesChannel and version management.

How it works

  1. Open the section
  2. Change one thing
  3. Verify it took effect

FAQ

Are API keys ever uploaded?

No. They stay in the local keystore and are used from your machine.

How does VIMS Settings connect to the rest of VIMS?

It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.

Related

VIMS DesktopLocal AI workspaceVIMS AgentAgent fleet and marketplaceVIMS SkillsAgent skillsVIMS MCPModel Context Protocol

Settings: models, keys, MCP, and voice

Settings is where the platform is wired: which models answer, which keys are used, which MCP servers auto-connect, how voice and personality behave, and what agents are allowed to do.

Open SettingsDownload VIMS