revealjs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVEALJS_HOST | No | Listen address. | 127.0.0.1 |
| REVEALJS_PORT | No | HTTP port (0 = random port). | 8000 |
| REVEALJS_DATA_DIR | No | Presentation storage directory. | ./presentations |
| REVEALJS_TRANSPORT | No | Transport mode: stdio, sse, or http. | stdio |
| REVEALJS_PUBLIC_URL | No | Base URL used by tool-returned URLs (set when behind a reverse proxy). | http://localhost:<port> |
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 |
|---|---|
| get_server_infoA | Get revealjs-mcp server info: reveal.js version, base URL and data directory. |
| list_themesA | List the bundled reveal.js themes usable as the |
| list_transitionsA | List the reveal.js slide transition styles usable as the |
| create_presentationA | Create a reveal.js presentation from an array of slides and serve it over HTTP. Each slide is one : raw HTML by default, or markdown when format is "markdown". Returns the browser-viewable URL. |
| list_presentationsA | List all presentations created by this server, with their URLs. |
| get_presentation_urlA | Get the browser-viewable URL of an existing presentation by id. |
| delete_presentationA | Delete a presentation by id. Returns whether anything was deleted. |
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 or resource: server info, theme/transition discovery, presentation lifecycle (list, create, get URL, delete). There is no overlap or ambiguity between any two tools.
All tool names follow a consistent verb_noun snake_case pattern, using get_, list_, create_, delete_ prefixes. The naming is uniform and predictable across the entire set.
Seven tools is well-scoped for a reveal.js presentation server, covering discovery, creation, and management without excess. Each tool serves a clear purpose in the workflow.
The CRUD-like lifecycle is mostly covered: create, list, get URL, and delete presentations. Missing an update/edit operation and a way to retrieve full presentation content, but these are minor gaps for the core use case.