marp

The Marp MCP server enables AI-assisted creation and editing of Marp presentations. It exposes a set of tools that let large language models manipulate Markdown slides, apply themes, and manage slide content in a structured way. With the default Marp theme as well as Gaia, Uncover, and Academic themes, you can generate polished slides from natural language prompts, adjust frontmatter for each slide, and perform layout operations such as inserting, updating, or removing slides. The server integrates a range of commands for listing layouts, generating slide IDs, and reading or mutating slides, making it easier for AI agents to compose cohesive slide decks as part of an automated workflow.

Prerequisites:

• Node.js and npm installed on your machine
• Access to run npm/npx commands

Installation steps:

1. Install or upgrade Node.js and npm if needed. You can verify with:

node -v
npm -v

2. Run the MCP client configuration to add the Marp MCP server. This uses npx to fetch the latest package and wire it into your MCP client:

# In your MCP client config (e.g., config.json for the client)
{
  "mcpServers": {
    "marp-mcp": {
      "command": "npx",
      "args": ["-y", "@masaki39/marp-mcp@latest"]
    }
  }
}

3. If you prefer to run directly in a development environment without editing client config, you can invoke the MCP server via npx:

npx -y @masaki39/marp-mcp@latest

Note: The server supports theme selection via command arguments, for example to choose a specific Marp theme:

{"command": "npx", "args": ["-y", "@masaki39/marp-mcp@latest", "-t", "default"]}

4. Ensure any dependency network access is allowed (some environments may block npm registry access).

Tips:

• The server includes an example Claude Code Skill for Marp integration. If you use the built-in CLI through Claude Code, you can create Marp presentations using the /marp command without additional MCP configuration.
• When selecting themes, you can mix and match the default Marp theme with Gaia, Uncover, or Academic.css for different presentation styles.
• If you encounter issues with layouts or slide IDs, use the list_layouts and read_slide tools to inspect the current slide set and verify IDs before performing mutations.
• For automated pipelines, pin the package version (e.g., @latest or a specific version) to ensure reproducible builds, and consider enabling verbose logging if debugging AI-driven slide edits.