slidev-orchestrator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLIDEV_BASE_PORT | No | Base port for dev servers (default 3030). | 3030 |
| SLIDEV_PRESENTATIONS_DIR | Yes | Path to the main folder containing presentations. Can also be provided via --dir CLI argument. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_presentationsA | List all Slidev presentations found in the presentations root directory (/app). A presentation is any sub-folder containing a slides.md. |
| create_presentationA | Scaffold a new Slidev presentation (folder + slides.md + package.json) in the root directory. Runs |
| start_serverA | Start the Slidev dev server for a presentation. Returns the local URL. Ports are allocated automatically unless |
| stop_serverB | Stop the running Slidev dev server of a presentation. |
| server_statusA | List all currently running Slidev dev servers (name, port, URL, pid). |
| select_presentationA | Target a presentation: connects to its official |
| call_slidev_toolA | Fallback passthrough: call a tool of the currently targeted presentation's official Slidev MCP by its original name. Useful for MCP clients that do not support dynamic tool list updates (tools/list_changed). |
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 7 tools
Each tool targets a distinct action: listing presentations, creating presentations, starting/stopping servers, checking server status, selecting a presentation, and calling a slidev tool. No two tools have overlapping purposes.
Most tools follow a clear verb_noun pattern (list_presentations, create_presentation, start_server, stop_server, select_presentation, call_slidev_tool). The exception is server_status, which is noun_noun; renaming it to get_server_status or list_servers would make the naming fully consistent.
With 7 tools, the server is well-scoped for its purpose of orchestrating Slidev presentations and their dev servers. Each tool earns its place and the count is not overwhelming.
The server covers the full lifecycle of presentation scaffolding and server management (create, list, start, stop, status), and provides access to the official Slidev MCP for editing slides. No major gaps are apparent for the stated purpose.