Marp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_presentationC | Initialize a new Marp presentation project with directory structure, theme, and templates |
| generate_slideC | Generate a slide using academic theme layouts (returns markdown string for copy-paste) |
| list_slide_layoutsB | List all available slide layouts with their parameters and descriptions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: generate_slide creates individual slide content, init_presentation sets up a new project structure, and list_slide_layouts provides information about available layouts. There is no overlap or ambiguity between these three functions.
All tools follow a consistent verb_noun naming pattern (generate_slide, init_presentation, list_slide_layouts) with clear, descriptive names that indicate their specific actions. The naming convention is uniform throughout the set.
With only 3 tools, this server feels somewhat thin for a presentation creation domain. While the tools cover core functions, additional operations like editing slides, managing themes, or exporting presentations would enhance completeness. The count is borderline but reasonable for a minimal implementation.
The tools cover initialization, layout listing, and slide generation, which are foundational for a presentation workflow. However, there are notable gaps: no tools for updating or deleting slides, managing presentation metadata, or exporting to formats like PDF or HTML. This limits the agent's ability to handle full presentation lifecycles.