Skip to main content
Automatic Configuration Provisioning pushes managed MCP server configurations directly into client applications. Admins mark servers as auto-synced in the dashboard, and the Runlayer CLI writes them into each developer’s tools.

​
How It Works

  1. Admin enables auto-sync on servers in the Runlayer dashboard
  2. CLI fetches configuration for auto-synced servers accessible to the user
  3. Client detection — the CLI auto-detects installed clients
  4. Config injection — server entries are written into each client’s config file
Enabling Auto Sync on a connector

​
Quick Start

# Install uv (package manager for the Runlayer CLI)
curl -LsSf https://astral.sh/uv/install.sh | sh

# Log in to Runlayer
uvx runlayer login --host https://your-instance.runlayer.com

# Sync all auto-synced servers to your clients
uvx runlayer setup sync -y
Credentials are stored in your OS keychain when available, with a fallback to ~/.runlayer/config.yaml. Use --client cursor to target a specific client. Run without -y to preview changes before applying.

​
Supported Clients

ClientmacOSWindows
Cursor✓✓
VS Code✓✓
Claude Desktop✓✓
Claude Code✓✓
Windsurf✓✓
Goose✓✓
Zed✓✓

​
MDM Deployment

For enterprise-wide deployment, use your MDM solution to run the sync command across all devices:

SimpleMDM

macOS deployment

Jamf Pro

macOS deployment

Mosyle

macOS deployment

Kandji

macOS deployment

Intune

Windows deployment