home / mcp / slidev builder mcp server

Slidev Builder MCP Server

Provides automatic backup, Git integration, and smart recovery for Slidev presentations via an MCP client.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "adolfosalasgomez3011-slidev-builder-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hatch/slidev-builder-mcp-v2"
      ]
    }
  }
}

You can run and manage professional Slidev presentations with built-in automatic protection, backup, and intelligent recovery through the MCP server. This setup helps you create, edit, and deploy slide decks confidently, knowing every change is automatically safeguarded and versioned.

How to use

Start by installing the MCP client globally or using a local npm/npx approach, then configure your MCP client to connect to the Slidev Builder MCP server. From there you can create protected decks, add slides, apply themes, and generate charts with automatic protection and easy recovery when needed.

Key usage patterns include creating protected decks, adding content, and applying themes while everything is automatically backed up and versioned. You can request smart recovery if content appears to be missing or corrupted, and you can perform manual backups or restorations when necessary.

How to install

npm install -g @hatch/slidev-builder-mcp-v2
```

```json
{
  "mcpServers": {
    "slidev-builder-v2": {
      "command": "npx",
      "args": ["-y", "@hatch/slidev-builder-mcp-v2"]
    }
  }
}
```

```bash
# Example runtime command for local development (if needed):
npx -y @hatch/slidev-builder-mcp-v2

Additional sections

Configuration is designed to be zero-configuration for protection features, but you can customize how you connect your MCP client to the server and what you want protected. The client JSON snippet shown here demonstrates how to point to the Slidev Builder MCP v2 server and enable automatic protection by default.

Protection in action is automatic for common operations. For example, creating a presentation, adding slides, or applying a theme all trigger backups, commits, and verifications. If content seems missing, you can use smart recovery to compare backups and restore to a previous version. You can also run manual backups and restoration if needed.

Examples of typical protected commands include creating a deck, adding slides with charts, and applying a corporate theme with automatic protection and rollback capabilities. All actions are tracked with backups and version history.

Available tools

create_deck_protected

Create presentations with automatic protection enabled, including auto-backup and versioned commits.

create_slide

Add slides with auto-backup and protection applied to the deck.

apply_theme

Apply corporate themes with rollback capability and protection checks.

generate_chart

Create charts with version control and automatic protection.

backup_presentation

Manual backup creation for a deck or presentation.

restore_presentation

Emergency recovery from backups with version history.

backup_status

Check the health and status of protection on a deck.

enable_protection

Activate protection for existing projects to start auto-protect.

create_component

Build reusable presentation components for reuse across decks.

list_components

Browse available reusable components.

add_component

Insert components into slides to enhance presentations.

publish_component

Share components with team members for collaboration.