What's new

This release makes Jaws AI-native. Jaws now ships a built-in Model Context Protocol (MCP) server, so you can point Claude Code, Claude Desktop, Cursor, Codex Desktop, or Codex CLI at your workspace and let the AI create projects, assemble deployment pipelines from your step templates, author new templates, set variables, and read deployment logs on your behalf. You pay your AI provider once — we don't resell tokens and we don't lock you to a model.

Getting connected is a two-step flow from Settings → AI assistants: pick a workspace, click your client, and copy the ready-to-paste config. Cursor even gets a one-click install link. Under the hood Jaws provisions a scoped service account, so every AI action is permission-checked and shows up in your audit log. Deploys stay safe by design — triggering is split into a dry-run preview and a token-gated trigger, and secret-typed variables are never read or written through the AI.

This release also refreshes the app with a new layout and updated styling, lets you bind step controls directly to variables — checkboxes, numbers, and dropdowns now resolve from your variable sets — and encrypts variable values at rest.

See the MCP feature overview or follow the 3-minute quickstart to connect your first client.

Highlights

Built-in MCP server with read, write, and deploy tools. One-click AI-client setup for Claude Code, Claude Desktop, Cursor, Codex Desktop, and Codex CLI. Refreshed app layout and styling. Step controls bound to variables, including checkboxes, numbers, and dropdowns. Encrypted variable values at rest.

Highlights

  • Built-in MCP server — drive Jaws from Claude Code, Claude Desktop, Cursor, Codex Desktop, or Codex CLI using the AI subscription you already have
  • One-click Connect AI client setup under Settings → AI assistants, with a scoped service account provisioned automatically
  • Safe by design: a dry-run preview_deploy precedes a token-gated trigger_deploy, and secret variables never travel through the AI
  • Refreshed app layout and styling
  • Bind step controls to variables — checkboxes, numbers, and dropdowns resolve from your variable sets
  • Encrypted variable values at rest