Skip to content

Updated

Mistral Vibe Code CLI

This guide uses LyraShield's integration registry for the cli surface. It shows the current setup strategy and client source; actual client loading and authenticated runtime acceptance are tracked separately below.

Connection setup

The registry's setup path for this client is Guided manual setup over local stdio.

Client activation instructions

Place shared skills in `.vibe/skills` in a trusted project or `~/.vibe/skills` for the user. Vibe MCP servers use `[[mcp_servers]]` entries in `./.vibe/config.toml` or `~/.vibe/config.toml`; the registry renderer does not write this array-table format, so use the official `vibe mcp add` flow or edit the file carefully. Vibe MCP currently does not support OAuth; a static API key does not substitute for hosted delegation.

Install type: No verified native MCP configuration is available for this client.
Place shared skills in `.vibe/skills` in a trusted project or `~/.vibe/skills` for the user. Vibe MCP servers use `[[mcp_servers]]` entries in `./.vibe/config.toml` or `~/.vibe/config.toml`; the registry renderer does not write this array-table format, so use the official `vibe mcp add` flow or edit the file carefully. Vibe MCP currently does not support OAuth; a static API key does not substitute for hosted delegation.
Manual setup: the pinned CLI package (lyrashield@0.2.14) has no matching installer contract for this integration. Use the configuration or client instructions above and verify the client loads it.

Important gotchas

  • The CLI and VS Code extension share configuration, but this registry entry documents the CLI surface. Vibe Code Web is a separate hosted surface.
  • Vibe skills can expose slash commands with `user-invocable: true`. Project-level skills load only after the workspace is trusted.
  • The official MCP reference says OAuth is not yet supported; static credentials such as an environment-backed API key are required for remote MCP.
Hosted access: use OAuth when the client supports it. Hosted mutations require a browser-confirmed delegation and are checked against its workspace, scope and expiry. An API key alone does not authorize hosted mutations. See the Remote MCP guide.
Local access: run npx -y lyrashield@0.2.14 login --oauth to select a workspace for local stdio, or use a scoped workspace API key in an appropriate private environment. Never commit credentials.

Native components and distribution

Documented client capabilities: skills, commands. These describe what the client can load; use the installer and distribution details below to see which LyraShield components are available for this surface.

Install shared LyraShield skills

The pinned CLI includes a skills installer for this client. Preview its file changes first, then run the install command. Existing files that are not LyraShield-owned, or have been customized, are preserved.

npx -y lyrashield@0.2.14 skills install mistral-vibe --project --dry-run
npx -y lyrashield@0.2.14 skills install mistral-vibe --project

Restart or reload the client and verify its skill list. Local files do not prove discovery, authentication, marketplace listing or runtime acceptance.

Distribution route: Direct Agent Skills and Vibe MCP configuration; registry state DIRECT. Client distribution documentation.

Support evidence

Registry tier: COMPATIBLE. Evidence: DOCUMENTATION, checked 2026-10-01. Client version: not recorded; tested platforms: not recorded. No client runtime receipt is recorded.Marketplace state and runtime compatibility are separate claims.

Source: Mistral Vibe Code CLI official documentation.